Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!amdcad!ames!nrl-cmf!ukma!gatech!udel!rochester!ur-tut!sunybcs!rutgers!im4u!ut-sally!utah-cs!utah-gr!uplherc!nrc-ut!nrcvax!mustang!lex
From: lex@mustang.UUCP (Lex Mierop)
Newsgroups: comp.unix.questions
Subject: Re: Cron
Message-ID: <119@mustang.UUCP>
Date: 20 Jan 88 22:03:12 GMT
References: <11098@brl-adm.ARPA> <449@wa3wbu.UUCP> <1988Jan17.235014.19530@lsuc.uucp>
Reply-To: lex@mustang.UUCP (Lex Mierop)
Organization: Ibis Systems Inc., Westlake CA
Lines: 22
Summary: no problem w/SunOS/BSD4.x

In article <1988Jan17.235014.19530@lsuc.uucp> dave@lsuc.UUCP (David Sherman) writes:
>In article <449@wa3wbu.UUCP> john@wa3wbu.UUCP (John Gayman) writes:
>>					At different times here,
>>if I make a change in the cron time-table, I do not re-boot the whole
>>machine. I simply kill the current cron job process and start it again
>>from the console. The time/jobs are read in at execution time.
>
>                          Perhaps you should check whether your
>supposition is really correct.

I am using SunOS3.4/BSD4.3 and in this system, cron sleeps between events
in the crontab file.  If you change the crontab file, all you have to do
is send signal #1 to cron and cron will wakeup and read the crontab file
to determine how long to sleep until the next event.  You can do this
by typing the following:

	kill -1 %d

where %d is the process id of cron.
-- 
Lex Mierop                             |  "Bandits, 11 o'clock low"
{psivax,trwind,..}!nrcvax!mustang!lex  |