syslog time problem

Where does syslog get it's idea of time?

After manually updating /etc/localtime to account for
the recent DST change, the other daemons get the message after
a restart and figure time correctly. But the -- MARK -- entries
from syslogd are still wrong, in spite of it being restarted
regularly from cron. This behaviour is consistant across several
old 2.2.xx machines. What am I missing here??

--
Jim Roy
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: syslog time problem

James Roy wrote:

> Where does syslog get it's idea of time?

It depends upon exactly which syslogd you are using, but they normally
just use libc functions (e.g. ctime).

> After manually updating /etc/localtime to account for
> the recent DST change, the other daemons get the message after
> a restart and figure time correctly. But the -- MARK -- entries
> from syslogd are still wrong, in spite of it being restarted
> regularly from cron. This behaviour is consistant across several
> old 2.2.xx machines. What am I missing here??

Have you checked that syslogd is actually getting restarted? It should
generate a log entry upon restart. Note that you actually have to kill
the old process and start a new one; sending it SIGHUP won't work.

--
Glynn Clements
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html