Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!cernvax!chx400!chx400!hslrswi!aut!jsmithso
From: jsmithso@aut.autelca.ascom.ch (Jim Smithson)
Newsgroups: comp.unix.sysv386
Subject: FYI : Side effect of increasing ULIMIT in /usr/lib/cron/logchecker
Keywords: ISC 2.2, ulimit, cron
Message-ID: <1751@aut.autelca.ascom.ch>
Date: 26 Apr 91 12:31:03 GMT
Organization: Ascom Autelca AG, CH-3073 Guemligen Switzerland
Lines: 21


I have seen a few articles about increasing the UNIX ulimit (maximum file size)
and people have correctly given the correct procedure to up the ulimit.
However there is one side effect of this that must be noted. The root cron job
which rolls over the cron log file uses the `ulimit` command to determine the
maximum size of the log file. So if you up the ulimit for the entire system you
will end up with HUGE cron log and olog files. I suggest you make changes to
the shell code in /usr/lib/cron/logchecker as below if you up the ulimit.

# set the high-water mark of the file
MARKER=4
#LIMIT=`ulimit`
LIMIT=250	#  change for ulimit increase
LIMIT=`expr $LIMIT - $MARKER`


-- 
James R. Smithson	Ascom Autelca AG      CH-3073 Guemligen/Switzerland
E-mail: jsmithso@autelca.ascom.ch   FAX: +41 31 529 544 Voice : +41 31 529 214
UUCP: ...!uunet!mcsun!chx400!hslrswi!aut!jsmithso
We are now landing in Bern, please turn your watch back 6 hours and 20 years.