En Mon, Aug 20, 2001 at 10:33:33AM +0800, Federico Sevilla III escribio:
#_
#_ While true this is only necessary when running programs that will spit
#_ out known messages regularly. sync shouldn't send anything to stderr, and
#_ if it does, you'd sure like to know, right?
#_
#_ >
http://www.linuxdoc.org/LDP/solrhe/Securing-Optimizing-Linux-RH-Edition-v1.3/gen-optim.html
#_ > ... talks about bdflush and buffermem.
<snip>
#_ My initial message about bdflush was meant to do something similar to
#_ running sync every second, by telling bdflush to flush ordinary data
#_ buffers onto disk at a maximum of 100 jiffies (1 second). IMHO this seems
#_ to be a "cleaner" implementation, compared to running sync every second.
#_ If I am wrong, someone please help enlighten me. I've sent this "bdflush
#_ vs sync" recommendation to the XFS list and haven't gotten any "sync is
#_ better" responses.
I tried the /dev/null entry, but I still get this:
Aug 20 15:24:00 bombastar CROND[4340]: (root) CMD (/bin/sync)
Aug 20 15:25:00 bombastar CROND[4340]: (root) CMD (/bin/sync)
Aug 20 15:26:00 bombastar CROND[4340]: (root) CMD (/bin/sync)
I supose it's because crond is the one talking to syslogd.
BTW this entry "* * * * * root /bin/sync" runs sync every minute because
that is cronds minimum increment. If I run sync every second, syslogd would
bring my system to it's knees ;->
--
Juan Miguel Cacho [EMAIL PROTECTED]
Philippines
...the poor count their blessings, the affluent count their calories.
_
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]
