Path: utzoo!utgpu!water!watmath!clyde!att!alberta!ubc-cs!uw-beaver!cornell!mailrus!ncar!boulder!sunybcs!canisius!sigmast!dgy
From: dgy@sigmast.UUCP (Dave Yearke)
Newsgroups: comp.unix.wizards
Subject: Re: CRON w/o logging (reprise)
Summary: If you rename or modify the log file, restart cron.
Keywords: ulimit OK
Message-ID: <591@sigmast.UUCP>
Date: 17 Aug 88 16:29:32 GMT
References: <755@mccc.UUCP>
Sender: nobody@cs.Buffalo.EDU
Reply-To: dgy@sigmast.UUCP (Dave Yearke)
Distribution: na
Organization: Sigma Systems Technology, Inc., Buffalo NY
Lines: 20

In article <755@mccc.UUCP> pjh@mccc.UUCP (Pete Holsberg) writes:
>
>I recently asked for help with a problem on a 3b2/400 running SysV R3.1.2.
>To wit, after a couple of days of norml operation, cron has stopped
>writing to /usr/lib/cron/log.  Several people have suggested that the
>file may be too big, and that I should check the ulimit.

I had the same problem when we first got our 3b2/500.  The answer to my
problem turned out to be this:  I had a weekly script that renamed the
log file to Old-Log, and created an empty log file.  This confused cron,
because I believe it always has log open for write, and can't deal with
the file disappearing or being modified by anything other than itself.

Once I added code to stop cron, then rename the file and create a new one,
then restart cron, the problem disappeared.

-- 
		Dave Yearke, Sigma Systems Technology, Inc.
		   5813 Main St, Williamsville, NY 14221
		  ...!{sunybcs,ames!canisius}!sigmast!dgy