From owner-freebsd-bugs  Thu Jul  6 12:40:02 1995
Return-Path: bugs-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id MAA27620
          for bugs-outgoing; Thu, 6 Jul 1995 12:40:02 -0700
Received: (from gnats@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id MAA27613
          ; Thu, 6 Jul 1995 12:40:01 -0700
Date: Thu, 6 Jul 1995 12:40:01 -0700
Message-Id: <199507061940.MAA27613@freefall.cdrom.com>
From: Alan Bawden <alan@beandorf.epilogue.com>
Reply-To: Alan Bawden <alan@beandorf.epilogue.com>
To: freebsd-bugs
Subject: misc/595: /var/cron/log doesn't rotate cleanly
In-Reply-To: Your message of Thu, 6 Jul 1995 15:30:41 -0400
	<199507061930.PAA01268@beandorf.epilogue.com>
Sender: bugs-owner@FreeBSD.org
Precedence: bulk


>Number:         595
>Category:       misc
>Synopsis:       /var/cron/log doesn't rotate cleanly
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs (FreeBSD bugs mailing list)
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jul  6 12:40:00 1995
>Originator:     Alan Bawden
>Organization:
ITS Preservation Society
>Release:        FreeBSD 2.0-RELEASE i386
>Environment:

	???

>Description:

	There are two different kinds of lines added to /var/cron/log:

	  root (06/27-13:15:01-241) CMD (/usr/libexec/atrun)
	  Jun 27 13:15:01 beandorf CRON[241]: (root) CMD (/usr/libexec/atrun) 

	The second line is generated by syslogd.  I don't know where the
	first line comes from, probably cron itself.  If you rotate the
	logs by renaming log -> log.0 -> log.1 -> ..., and then send a
	SIGHUP to syslogd, the syslogd lines will start to accumulate in
	the new file, but the other lines will continue to accumulate in
	the file now named `log.0'.

	This sequence of events usually happens after /etc/weekly runs at
	3:30 AM Saturday (which does the renaming) followed by /etc/daily
	at 2:00 AM Sunday (which sends the SIGHUP).

	These logs would be much more readable if all the information they
	contained always accumulated at the end of the same file...

>How-To-Repeat:

	Take a look at the cron logs from any plain FreeBSD 2.0 machine
	just after the daily runs at 2 AM Sunday.

>Fix:
	
	I have no idea.

>Audit-Trail:
>Unformatted: