Hi,
>For this reason, the lack of cron logging is
>minor as compared to the possible consequences.
Of course you're right. But on the other hand...
>CRONLOG=NO in /etc/default/cron.
...is some kind like a brute force method, it results in nothing being
logged by cron and sometimes for debugging it makes definetely sense to log
outputs of cron jobs. So I still recommend using the redirection to
/dev/null on each cron entry, in case you need the output it's easy to
change the setting for that cron job without having to restart anything.
Note: If you place the following lines...
EDITOR=vi
export EDITOR
...in the file /usr/fox/bin/VT100.script befor the shelltool is invoked, you
can very easily edit the cron while it is running using vi with typing the
command
# crontab -e
at the Shell prompt. If you save your changes you can check it's success
instantly with
# crontab -l
Note, that /usr/fox/bin/VT100.script is overwritten by some foxboro
installation processes and that changes there maybe have to be
re-implemented afterwards.
best regards -
Marcel Sieling
Systems Technologies
FOXBORO Deutschland GmbH
Heerdter Lohweg 53 - 55
40549 Duesseldorf
Tel.: +49 (0)211 5966-171
Fax: +49 (0)211 5966-104
Mobile: +49 (0)172 2673077
E-Mail: [EMAIL PROTECTED]
http://www.foxboro-deutschland.de
Private Home: http://www.powerslider.de
> -----Ursprüngliche Nachricht-----
> Von: Jack Easley [SMTP:[EMAIL PROTECTED]]
> Gesendet am: Dienstag, 20. März 2001 15:23
> An: [EMAIL PROTECTED]
> Betreff: Crontab Log
>
>
>
> 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]
-----------------------------------------------------------------------
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]
