Scheduled operations

Kronodoc uses the cron daemon to run background tasks such as sending notifications and messages, cleaning removed documents and generating indexes for text searches at specific times of the day or week.

$ crontab -l 

The command outputs all periodical tasks that are scheduled to be run by the user issuing the command. Please note that this list may contain also other commands besides the Kronodoc periodical commands. The list may look similar to the following.

27 5 * * 1-5 (cd "/home/kronodoc/kd40/Kronodoc"/KRONO/bin; ./runbatch.sh daily) >/dev/null 2>&1
32 5 * * * (cd "/home/kronodoc/kd40/Kronodoc"/KRONO/bin; ./runbatch.sh everyday) >/dev/null 2>&1
37 5 * * 1 (cd "/home/kronodoc/kd40/Kronodoc"/KRONO/bin; ./runbatch.sh weekly) >/dev/null 2>&1
4,14,24,34,44,54 * * * * (cd "/home/kronodoc/kd40/Kronodoc"/KRONO/bin; ./ntf-immediate-poll.pm) >/dev/null 2>&1

These tasks are scheduled automatically by the installation script. For this to be possible, cron services need to be allowed for the used ID with which Kronodoc is run. For example on a standard HP-UX and Solaris systems you need to add the user ID under which Kronodoc is run to the list of usernames in the file /usr/lib/cron/cron.allow or /etc/cron.d/cron.allow. To do that run the following command as root.

$ echo Kronodoc >>/usr/lib/cron/cron.allow