Fix skipped daily in Eastern Europe

- Move /etc/daily from 03:15 -> 04:15
- Move /etc/weekly from 04:30 -> 05:30 (to keep the spacing)

This should prevent problems during daylight savings changeover (which
is usually between 01:00 -> 04:00, depending upon the region) where the
cronjobs may be executed twice, or never at all...

This expands on the previous fix in revision 1.13 from 1997.

Set a CRON_WITHIN of 7200 (2 hours). This should not be noticed on
most machines, but ones that are slept overnight (like laptops) will
no longer suddenly have all overnight jobs start simultaneously upon
awakening, rendering the machine useless. I thought I had done this
long ago, but it turned out I'd only done it for my own machines.

* daily/weekly/monthly:
- change to always output a valid To: and Subject: line.
- To: recipient obtained from $MAILTO (defaults to root).
- add date to Subject: line. closes [bin/4526] from Giles Lean
<giles@nemeton.com.au>
* daily: explicitly print 'Nothing to report' if /etc/security didn't
report anything.
* crontab: pass output of scripts through sendmail -t instead of

Move /etc/daily from 02:00 -> 03:15, and /etc/weekly from 03:30 -> 04:30.
Should prevent problems during daylight savings changeover (which is usually
between 01:00 -> 03:00, depending upon the region) where the cronjobs
may be executed twice, or never at all...

branches: 1.12.2;
include hostname in subject of email with results of running *ly
scripts; from Jim Bernard in PR misc/3996

remove redundant path directories.

0-59/10 -> */10

New-style RCS ids.

daily, montly, weekly no longer special

run atrun every 10 minutes

update for new cron

arrange for all log rotations to be handled by /usr/bin/newsyslog

Added /etc/rpc for librpc support
fixed crontab so it works (oops)
fixed /etc/daily whatis.db support

cleaned up header

installs crontab in right place

branches: 1.1.1;
Initial revision

Set a CRON_WITHIN of 7200 (2 hours). This should not be noticed on
most machines, but ones that are slept overnight (like laptops) will
no longer suddenly have all overnight jobs start simultaneously upon
awakening, rendering the machine useless. I thought I had done this
long ago, but it turned out I'd only done it for my own machines.

* daily/weekly/monthly:
- change to always output a valid To: and Subject: line.
- To: recipient obtained from $MAILTO (defaults to root).
- add date to Subject: line. closes [bin/4526] from Giles Lean
<giles@nemeton.com.au>
* daily: explicitly print 'Nothing to report' if /etc/security didn't
report anything.
* crontab: pass output of scripts through sendmail -t instead of

Move /etc/daily from 02:00 -> 03:15, and /etc/weekly from 03:30 -> 04:30.
Should prevent problems during daylight savings changeover (which is usually
between 01:00 -> 03:00, depending upon the region) where the cronjobs
may be executed twice, or never at all...

branches: 1.12.2;
include hostname in subject of email with results of running *ly
scripts; from Jim Bernard in PR misc/3996

remove redundant path directories.

0-59/10 -> */10

New-style RCS ids.

daily, montly, weekly no longer special

run atrun every 10 minutes

update for new cron

arrange for all log rotations to be handled by /usr/bin/newsyslog

Added /etc/rpc for librpc support
fixed crontab so it works (oops)
fixed /etc/daily whatis.db support

cleaned up header

installs crontab in right place

branches: 1.1.1;
Initial revision

import 4.4BSD-Lite

initial import of 386bsd-0.1 sources

Pull rev 1.13 up from trunk (lukem)