On Mon, 20 Aug 2001 at 15:31, Juan Miguel Cacho wrote:
> 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)
Adding that redirection to /dev/null just means that sync won't send stuff
to stderr which in turn means that cron won't e-mail you with the "error
message". But yes, it will properly notify syslog of the actions. Wouldn't
you like to know when cron is doing things as root "behind your back"? :)
> I supose it's because crond is the one talking to syslogd.
Indeed, and it _should_ in most cases. If you want to limit your syslog
you can edit syslog.conf and say ... tell it to only log urgent messages.
Or even not log at all. Don't just quit syslog, though, as if you do
anything that should have gone to syslog will probably find its way to
your console that that'd be ugly. Instead tell syslog to log everything to
/dev/null. Hahaha. :)
> 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 ;->
Oops. Oo nga pala. Then the bdflush approach is even better, since it can
flush dirty buffers to disk every second. Unfortunately it can't flush
dirty data buffers to disk less than this, although metadata is, by
default, flushed to disk every 60 jiffies, or 0.60 seconds. :)
I still wonder, though, is this the same as running sync (less the syslog
entries, of course)? I think so, but some guru has yet to validate my
"research" of sorts. :)
--> Jijo
--
Federico Sevilla III :: [EMAIL PROTECTED]
Network Administrator :: The Leather Collection, Inc.
GnuPG Key: <http://jijo.leathercollection.ph/jijo.gpg>
_
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]
