Anyone have any ideas about this? Perhaps I'm not used to a not-so-active machine..but it seems I have way too many "mark"s in my /var/log/messages file -- 1289 since dec 1 Jan 3 00:00:05 box su: (to nobody) root on none Jan 3 00:16:57 box -- MARK -- Jan 3 00:36:57 box -- MARK -- Jan 3 00:56:57 box -- MARK -- Jan 3 01:16:57 box -- MARK -- Jan 3 01:36:57 box -- MARK -- Jan 3 01:56:57 box -- MARK -- Jan 3 02:16:57 box -- MARK -- Jan 3 02:36:57 box -- MARK -- Jan 3 02:56:57 box -- MARK -- Jan 3 03:16:57 box -- MARK -- Jan 3 03:36:57 box -- MARK -- Jan 3 03:56:57 box -- MARK -- Jan 3 04:16:57 box -- MARK -- etc etc etc
On Mon, 3 Jan 2000, Chrissy LeMaire wrote:
Anyone have any ideas about this? Perhaps I'm not used to a not-so-active machine..but it seems I have way too many "mark"s in my /var/log/messages file -- 1289 since dec 1
Jan 3 00:00:05 box su: (to nobody) root on none Jan 3 00:16:57 box -- MARK --
See "man syslogd", search for MARK there. Per default, syslogd writes to
the log file every 20 minutes. This is handy if you have problems with
your machine, then you can see when the machine went down.
You can add extra options to syslogd in /etc/rc.config (SYSLOGD_PARAMS).
I guess using -m0 will disable the logging.
--
==============================================================================
Erwin Andreasen Herlev, Denmark
On Mon, 3 Jan 2000, Erwin S. Andreasen wrote:
You can add extra options to syslogd in /etc/rc.config (SYSLOGD_PARAMS).
I guess using -m0 will disable the logging.
Oops, I guess I should have tried it before posting :)
-m0 will set the interval to half a minute. There doesn't seem to be any
way to disable it looking at the source, just set it to e.g. -m 1440 to do
it only once daily.
--
==============================================================================
Erwin Andreasen Herlev, Denmark
"Erwin S. Andreasen" wrote:
On Mon, 3 Jan 2000, Erwin S. Andreasen wrote:
You can add extra options to syslogd in /etc/rc.config (SYSLOGD_PARAMS).
I guess using -m0 will disable the logging.
Oops, I guess I should have tried it before posting :)
-m0 will set the interval to half a minute. There doesn't seem to be any way to disable it looking at the source, just set it to e.g. -m 1440 to do it only once daily.
not sure what you are using, but on my SuSE 6.3 the syslogd manpage says: ---snip--- -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. ---snap--- not sure though, 'cause i haven't played with this *greetz* from Vienna Hannes -- Johann Georg Hautzinger, email: trema@eic.at, Tel.: 531 00 1907 Erste Bank AG - OE 0423 - Orga./Entw. Treasury u. Orga.Wertpapier Boersegasse 14, 1010 Wien http://treasury.erstebank.at
On Mon, 3 Jan 2000, Johann G. Hautzinger wrote:
I guess using -m0 will disable the logging.
Oops, I guess I should have tried it before posting :)
-m0 will set the interval to half a minute. There doesn't seem to be any way to disable it looking at the source, just set it to e.g. -m 1440 to do it only once daily.
not sure what you are using, but on my SuSE 6.3 the syslogd manpage says:
[...]
Setting the interval to zero turns it off entirely.
Oh, I was looking at the sysklogd-1.3-30 source package from SUSE 6.2 --
they probably added -m0 in whatever version is in 6.3.
--
==============================================================================
Erwin Andreasen Herlev, Denmark
Hi, Chrissy LeMaire wrote:
Anyone have any ideas about this? Perhaps I'm not used to a not-so-active machine..but it seems I have way too many "mark"s in my /var/log/messages file -- 1289 since dec 1
Jan 3 00:00:05 box su: (to nobody) root on none Jan 3 00:16:57 box -- MARK -- Jan 3 00:36:57 box -- MARK -- Jan 3 00:56:57 box -- MARK -- Jan 3 01:16:57 box -- MARK -- Jan 3 01:36:57 box -- MARK -- Jan 3 01:56:57 box -- MARK -- Jan 3 02:16:57 box -- MARK -- Jan 3 02:36:57 box -- MARK -- Jan 3 02:56:57 box -- MARK -- Jan 3 03:16:57 box -- MARK -- Jan 3 03:36:57 box -- MARK -- Jan 3 03:56:57 box -- MARK -- Jan 3 04:16:57 box -- MARK --
You should have a look on the man page of 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. You can set the interval of logging the mark. This is sometimes helpfull, wenn a script tails the syslog an gets periodically an activity ;-) -- MfG, M.Stahn ++ The software said it requires Windows 95 or better, ++ ++ so I installed Linux! ++
This is done by the syslogd daemon. You can configure the frequency with the -m <interval> switch. The default is 20 minutes (which is exactly what you're seeing). When you set it to "0", the marks are turned off. Karl Heinz On Mon, Jan 03, 2000 at 04:38:44AM -0800, Chrissy LeMaire wrote:
Anyone have any ideas about this? Perhaps I'm not used to a not-so-active machine..but it seems I have way too many "mark"s in my /var/log/messages file -- 1289 since dec 1
Jan 3 00:00:05 box su: (to nobody) root on none Jan 3 00:16:57 box -- MARK -- Jan 3 00:36:57 box -- MARK -- Jan 3 00:56:57 box -- MARK -- Jan 3 01:16:57 box -- MARK -- Jan 3 01:36:57 box -- MARK -- Jan 3 01:56:57 box -- MARK -- Jan 3 02:16:57 box -- MARK -- Jan 3 02:36:57 box -- MARK -- Jan 3 02:56:57 box -- MARK -- Jan 3 03:16:57 box -- MARK -- Jan 3 03:36:57 box -- MARK -- Jan 3 03:56:57 box -- MARK -- Jan 3 04:16:57 box -- MARK --
etc etc etc
-- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com
-- Karl Heinz Kremer khk@khk.net http://www.khk.net ICQ: 41190739
participants (5)
-
Chrissy LeMaire -
Erwin S. Andreasen -
Johann G. Hautzinger -
Karl Heinz Kremer -
Martin Stahn