Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!munnari.oz.au!labtam!cmsfl!nigel
From: nigel@cmsfl@labtam.oz (Nigel Harwood)
Newsgroups: comp.sys.ncr
Subject: cronlogs on 600 & 650
Keywords: cron logs 600 650
Message-ID: <366@cmsfl>
Date: 1 Mar 90 05:59:45 GMT
Organization: Coles Myer Ltd., Melbourne, Australia
Lines: 28

The Tower 32/650 under 2.01.01 has a nice feature where cron automatically
limits its /usr/lib/cron/log to a reasonable size.

This feature is not available on a Tower 32/600 under 1.03.00.

Any suggestions on the best way to do this ?

It sounded trivial to me initially until I found that cron keeps its
log open.  This means that if I do anything like copying the last
1000 lines to a new file and then moving the new file over the old,
cron will still have the handle to the old file.  As well as the problem
of the data cron is writing in the mean time.

Sounds to me like I need to stop cron and then deal with the log, restarting
it when I have finished.

I would however like to know if a nicer way exists than 'kill'ing it,
i.e. I wouldn't know what would happen to commands cron was running
at the time it was killed.

Comments, advice ?

Regards
-- 
<<<<<<<<<<<<<<<<<<<<<<<  Nigel Harwood  >>>>>>>>>>>>>>>>>>>>>>>>>
<< Post:  Coles Myer Ltd, PO Box 2000 Tooronga 3146, Australia >>
<< Phone: +61 3 829 6090      E-mail: nigel%cmsfl@labtam.oz.au >>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>