Version 1.1: The second version number was changed because there is 
a number of smaller but visible changes since 1.0.0. There is also a
new possibility to attempt the restart of interrupted commands after
reboot.

Version 1.0: Added a possibility to start commands directly from the 
crontab command line.

Version 0.4 re-reads only modified crontabs which makes it better for
larger boxes, the crontab command is based on pipes now and allows
feedback and some minor improvements.

Some crontab options in 0.3 have changed. Take a look at the examples.

While most cron implementations are optimized for large installations,
this one is is mainly intended for systems that are frequently down, can
start commands after reboot if necessary and allows to specify commands
relative to the system uptime. Normally it will replace an existing cron.

INSTALLATION:

1) Take a look at the Makefile for compile-time defaults.

2) Type make

3) Become root and type make install. If you have another cron you
   should either backup /usr/sbin/crond and /usr/bin/crontab or change
   the /usr prefix in Makefile to /usr/local before you do this.
   To avoid paranoia, make install will create the following files:

   PREFIX/sbin/crond              The daemon
   PREFIX/bin/crontab		  Command to maintain crontabs 
   PREFIX/bin/dtime		  Displays the uptime counter
   PREFIX/man/man1/crontab.1	  
   PREFIX/man/man1/dtime.1
   PREFIX/man/man8/crond.8
   /usr/doc/crond/		  
   /var/lib/crontabs		  Directory with crontab files.

   During the first startup, the file /var/log/uptime will also be created
   to save the system uptime counter.

4) Install crontab files in /var/lib/crontabs but read the manpages first.
   There is a file crontab.sample included. The name for the root crontab
   is defined in Makefile and can be changed there. Make sure that the
   crontab directory has standard permissions 0755.

   If you have installed in /usr/local, make sure there is no name conflict
   with an existing cron. Probably you have to rename one of the crontab
   commands or use absolute pathnames. 

5) Start crond for a test and take a look at syslog. Try dtime to see
   if it counts the system uptime. The rc line to start at boot time could
   look like /sbin/crond -l /var/log/cron -b to enable the FIFO queue and 
   logfile.
