Actually, syslogd does write all of it. There is a very good explanation of why in the latest Server/Workstation Expert magazine. If each process touched that file, you'd have a real mess as multiple apps tried to append to the same file. That's why syslogd was created. Stew Benedict On Wed, 20 Sep 2000, Ron Johnson, Jr. wrote: > David Mihm wrote: > > > > On Wed, 20 Sep 2000, Ron Johnson, Jr. wrote: > > > > > As you can see, these are logged every 20 minutes, and it's been > > > happening since the beginning of the machine. What causes this, > > > and can I or should I turn this off? > > > > > > Sep 20 01:52:31 rebel -- MARK -- > > > > >From the man page for syslogd: > > > > -m interval > > The syslogd logs a mark timestamp regularly. The > > default interval between two -- MARK -- lines is 20 > > minutes. This can be changed with this option. > > Setting the interval to zero turns it off entirely. > > > > ... from someone who writes man pages, man pages are your friend. :) > > > > Thanks. I'd have *never* thought to look in the man page. > Stuff is written in /var/log/messages from so many sources, > who'da thunk that syslogd does it? > > In hindsight, though, since a process name isn't listed, I should > have realized (by process of elimination) that syslogd does it. > > Ron > -- > +----------------------------------------------------------+ > | Ron Johnson, Jr. Home: [EMAIL PROTECTED] | > | Jefferson, LA USA WWW : [EMAIL PROTECTED] | > | | > | Most overused words: feel, cool/kewl, fun, myBlah.com | > | Most underused word: think | > +----------------------------------------------------------+ > >
Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
