This document may have been updated since your installation. You can find the latest version at http://docs.kde.org/development/en/tdepim/.
7.1. | What is the alarm daemon? |
The alarm daemon is an application which runs in the background, monitoring alarms and telling KAlarm to trigger them when they become due. | |
7.2. | What configuration files does KAlarm use? |
The file The calendar file which stores your pending alarms is
The calendar file which stores your expired alarms is
The calendar file which stores your alarm templates is
Details of alarms currently being displayed are stored in the
calendar file
| |
7.3. | What configuration files does the alarm daemon use? |
The file | |
7.4. | 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 tdepim
applications. KAlarm uses certain non-standard properties in the
Alarm component, in conformance with RFC2445:
| |
7.5. | What are the application names of KAlarm and the alarm daemon? |
KAlarm's application name is kalarm, and the alarm daemon's application name is kalarmd. |
Would you like to comment or contribute an update to this page?
Send feedback to the TDE Development Team