Chapter 6. Questions and Answers

This document may have been updated since your installation. You can find the latest version at http://docs.kde.org/.

6.1. What configuration files does KAlarm use?
6.2. Where does KAlarm store its alarms?
6.3. What format are alarms stored in?
6.4. What is the program kalarmautostart?

6.1.

What configuration files does KAlarm use?

$KDEHOME/share/config/kalarmrc holds your KAlarm preferences.

$KDEHOME/share/config/kresources/alarms/stdrc holds your alarm calendar configuration.

($KDEHOME is usually ˜/.kde or similar.)

6.2.

Where does KAlarm store its alarms?

The names of the calendar files which KAlarm creates the first time it is run are as follows (but these may be overridden by entries in the General section of KAlarm's preferences file):

  • $KDEHOME/share/apps/kalarm/calendar.ics holds active alarms (overridable by the Calendar entry).

  • $KDEHOME/share/apps/kalarm/expired.ics holds archived alarms (overridable by the ExpiredCalendar entry).

  • $KDEHOME/share/apps/kalarm/template.ics holds alarm templates (overridable by the TemplateCalendar entry).

You can find out which calendar files are currently in use by viewing each calendar's details in the alarm calendars list. The file names are stored in the alarm calendar configuration file.

Details of alarms currently being displayed are stored in the calendar file $KDEHOME/share/apps/kalarm/displaying.ics.

6.3.

What format are alarms stored in?

The calendar files in which KAlarm stores its alarms are text files whose format is defined by the document RFC2445 - Internet Calendaring and Scheduling Core Object Specification (iCalendar). This is the standard format used by all kdepim applications. KAlarm uses certain non-standard properties, in conformance with RFC2445. These are documented in the DESIGN.html file which is distributed with KAlarm.

6.4.

What is the program kalarmautostart?

kalarmautostart is a little helper program whose function is to autostart KAlarm at login.

KAlarm is usually restored by the session manager at login (to redisplay its windows in the same state as they were when you logged off). But if it was not running when you logged off, it would not be started by the session manager and therefore needs to be autostarted. The problem is that when an application is both session managed and autostarted, there is no guarantee as to which will occur first. If autostart gets in first, it will prevent the session manager from restoring the application's state.

To avoid this problem, kalarmautostart is autostarted at login instead of KAlarm. All it does is wait for a short time (to ensure that the session manager has time to do its job) before starting KAlarm, at which point it terminates.