crontab: Sunday=7, not 0.

[Larry Lippman]

> (Admittedly, the S5R2 "cron" is
> also somewhat different; "crontab"s have the same format, but they live in
> different places and every user gets one of their own, to have, hold, and
> alter.)

	I had a lot of "fun" with the new `cron' arrangement when we upgraded
our 3B2 to Sys V Release 2.  Since I had many things on my mind to get our
upgraded machine back into service, I never CAREFULLY read the doc's on crontab
use to discover the ``crontab'' COMMAND.  So, I merely edited the default
file for /usr/spool/cron/crontabs/root with my additional crontab entries -
which promptly did not work.  I tried this several times, and no matter what
I put in that crontab file, nothing would execute unless I rebooted the system.
Even the AT&T Hotline did not know what was wrong.
	Finally, I discovered the ``crontab'' COMMAND and READ the manual page.
Success - it worked.
	My question: does anyone know why simply editing the particular crontab
file will not work, and why the crontab command MUST be used?

===  Larry Lippman @ Recognition Research Corp., Clarence, New York        ===
===  UUCP    {decvax,dual,rocksanne,rocksvax,watmath}!sunybcs!kitty!larry  ===
===  VOICE   716/741-9185		 {rice,shell}!baylor!/             ===
===  FAX     716/741-9635 {AT&T 3510D}	             ihnp4!/               ===
===									   ===
===                   "Have you hugged your cat today?"		           ===