Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!atexnet!donovan From: donovan@atexnet.UUCP (Dennis Donovan) Newsgroups: comp.unix.questions Subject: Re: crontab update Message-ID: <647@hawkeye.atexnet.UUCP> Date: 14 Mar 90 13:05:14 GMT References: <1990Mar1.195750.25818@eng.umd.edu> <1990Mar9.234707.7782@eci386.uucp> <3025@auspex.auspex.com> <1990Mar14.003245.2932@llustig.uucp> Reply-To: donovan@hawkeye.UUCP (Dennis Donovan) Distribution: na Organization: EPPS (A Kodak Co.),Bedford,MA Lines: 29 In article <1990Mar14.003245.2932@llustig.uucp> david@llustig.UUCP (David Schachter) writes: >Someone wrote: >>>The *only* documented and reliable ways of getting cron to recognize >>>a new crontab is to use the crontab command. > >Or become root, kill cron, change/add/delete crontab stuff, and re-invoke >cron. Violent, but effective. Not, perhaps, documented, but reliable. Quite. > I just did this the other day. I'm on a Sun 3/60. I updated crontab then sent a Hangup Signal to the cron process with: "kill -HUP ##" where ## is the process ID from "ps" It worked fine!! -------------------------------------------------------------------------------- +----------------------------------------------------------+ | Dennis L. Donovan | | UUCP : !uunet!atexnet!donovan | | AT&T : (617) 276-7349 | | USMAIL : Electronic Pre-Press Systems, Inc (EPPS,ATEX) | | 32 Wiggins Ave., M.S. 231/32W | | Bedford, MA 01730 | +----------------------------------------------------------+ "Nobody asked, just my opinion" Disclaimer: The views expressed are my own, I doubt if ATEX really cares anyway.