Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/5/84; site kitty.UUCP Path: utzoo!watmath!clyde!cbosgd!ihnp4!mhuxn!mhuxr!ulysses!allegra!mit-eddie!think!harvard!seismo!rochester!ritcv!rocksvax!rocksanne!sunybcs!kitty!larry From: larry@kitty.UUCP (Larry Lippman) Newsgroups: net.unix Subject: Re: Re: crontab: Sunday=7, not 0. Message-ID: <573@kitty.UUCP> Date: Mon, 11-Nov-85 20:30:33 EST Article-I.D.: kitty.573 Posted: Mon Nov 11 20:30:33 1985 Date-Received: Thu, 14-Nov-85 20:44:34 EST References: <704@adobe.UUCP> <187@l5.uucp> <491@ttidcb.UUCP> <2935@sun.uucp> Organization: Recognition Research Corp., Clarence, NY Lines: 24 > (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?" ===