Path: utzoo!mnetor!uunet!husc6!cmcl2!nrl-cmf!ames!pasteur!ucbvax!alias.UUCP!ktureski
From: ktureski@alias.UUCP (Kevin Tureski)
Newsgroups: comp.sys.sgi
Subject: Re:  Problems with cron
Message-ID: <8804291859.AA21406@csri.toronto.edu>
Date: 29 Apr 88 15:54:40 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 23


	Has anybody noticed [that cron tends to run things twice]? What can 
	be done to get around it?
	Our environment: 4D/70G, Unix Release 4D1-2.0
	
							Urs Meyer
	
Yes, we've noticed it and complained about it. The answer: wait for 3.0. Now 
we've got 3.0 (an early VAR release) and the problem has disappeared. In the
meantime, you might consider a simple lockout mechanism for your own commands
that are to be run via the crontab. If you're not sure whether cron is running
things twice, then try the following entry in a crontab:

	00,10,20,30,40,50 * * * * date >> /tmp/date


Kevin Tureski
Alias Research Inc.
110 Richmond St E. 
Toronto Canada M5C 1P1
416 362-9181

UUCP:	{allegra,ihnp4,watmath!utai}!utcsri!alias!ktureski