home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!spool.mu.edu!think.com!rpi!batcomputer!cornell!uw-beaver!uw-coco!quick!victrola!vince
- From: vince@victrola.sea.wa.us (Vince Skahan)
- Subject: Re: cron gets stuck.
- References: <1992Nov2.174856.22567@muug.mb.ca>
- Organization: Vince and Suzie's Underpowered PC
- Date: Wed, 4 Nov 1992 18:58:28 GMT
- Message-ID: <1992Nov4.185828.150@victrola.sea.wa.us>
- Lines: 22
-
- In article <1992Nov2.174856.22567@muug.mb.ca> gkm@muug.mb.ca (Greg K. Moeller) writes:
- >I'm using cron to spawn UUCP and news shells, etc.
- >The problem is that when I replace the crontab entry for either of these
- >(crontab -u news -r news.tab[as root]) the entryy gets replaced ok, but cron
- >gets stuck. It doesn't do anything for anyone at all. I have to kill it
- >and restart it. From my reading of the docs for cron, it's supposed to
- >notice that the file has changed, and re-read it.
- >
-
- I've found that if I change a crontab entry, I have to do a "
- "kill `cat /etc/cron.pid` ; /etc/crond"
- to get cron to reinitialize off the new entry. I tried a kill -HUP but
- it killed it dead rather than re-initializing off the files.
-
-
-
-
-
-
- --
- ---------- Vince Skahan --------- vince@victrola.sea.wa.us ----------
- Running Linux/C-news/trn/Elm/Smail - we don't need no steenkin' MS-DOS
-