home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!caen!destroyer!ais.org!lcd
- From: lcd@ais.org (Leon Dent)
- Subject: Re: cron gets stuck.
- Message-ID: <Bx9rB9.6r5@ais.org>
- Organization: UMCC
- References: <1992Nov2.174856.22567@muug.mb.ca> <1992Nov4.185828.150@victrola.sea.wa.us>
- Date: Fri, 6 Nov 1992 00:42:42 GMT
- Lines: 22
-
- In article <1992Nov4.185828.150@victrola.sea.wa.us> vince@victrola.sea.wa.us (Vince Skahan) writes:
- >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.
-
- Yeah, but its supposed to work accroding to the docs. If you are running
- a multi-user system, is each user supposed to send mail to root to re-start
- cron every time they change an entry?
-
- Leon Dent
- lcd@ais.org
-
-