I believe recommended procedure to stop cron logging is to change the statement
CRONLOG=YES to CRONLOG=NO in /etc/default/cron. You must stop/start the cron
process after this to make the changes take effect. From the borne shell, use
/etc/init.d
/cron stop to stop cron, then /etc/init.d/cron start to start cron.I also make
it a rule to
append every line I enter into cron with "> /dev/null 2>&1".
The worst mistake I have ever made on the Fox occurred when the cronlog was
enabled
and a new scheduled cron process & errors was not redirected to cron. This
particular
dwprocess accidently created a large cronlog and filled the /var partition
overnite! Your
Fox machines will not run with a full /var partition as space is required for a
lot of normal
Foxboro processes. The result was a lockup of all Foxboro machines. Not Good!
For
this reason, the lack of cron logging is minor as compared to the possible
consequences.
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All
postings from this list are the work of list subscribers and no warranty
is made or implied as to the accuracy of any information disseminated
through this medium. By subscribing to this list you agree to hold the
list sponsor(s) blameless for any and all mishaps which might occur due to
your application of information received from this mailing list.
To be removed from this list, send mail to
[EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
