You might want to try directing std-out of the cron output to /dev/null. On
the Vixie cron, the std-err will still get mailed to the crontab owner unless
you override the MAILTO.
* * * * * /bin/sync > /dev/null
BTW, you may want to check out
http://www.linuxdoc.org/LDP/solrhe/Securing-Optimizing-Linux-RH-Edition-v1.3/gen-optim.html
... talks about bdflush and buffermem.
Quick question though. I did not quite recognize the syntax on the crontab
entry you sent the list
* * * * * root /bin/sync
^^^^
Is this a linux system with the Vixie cron?
On Saturday 18 August 2001 15:00, Juan Miguel Cacho wrote:
> En Sat, Aug 18, 2001 at 02:46:04PM +0800, Paolo escribio:
> #_ Juan Miguel Cacho wrote:
> #_ >
> #_ > Anyway, I'll just leave the darned thing there, the only problem is
> #_ > that it fills up the log.
> #_ >
> #_ Use logrotate then. But hey! 17 GB!?!?!?!
>
> Don't worry I still use logrotate, in fact I set it to rotate sooner and
> keep fewer archives.
_
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
To subscribe to the Linux Newbies' List: send "subscribe" in the body to
[EMAIL PROTECTED]
