Subject: Re: localtime and chroot issues
To: None <email@example.com>
From: Ian Zagorskih <firstname.lastname@example.org>
Date: 05/06/2004 15:09:54
=F7 =D3=CF=CF=C2=DD=C5=CE=C9=C9 =CF=D4 6 =ED=C1=CA 2004 14:48 Simon J. Gerr=
> >that tftpd daemon runs as chroot-ed process in default /tftproot dir so =
> >course it couldn't access /etc/localtime to get the proper timezone
> >information. Ok, i made a copy of localtime in tftpd's sandbox so it fee=
> >happy now.
> A good solution is to modify syslog(3) to just send bare utc seconds
> (suitably tagged) and have syslogd do the conversion to localtime.
> This involves a change to the protocol b/w syslog and syslogd,
> but provided you also handle the old format - and use that when
> sending off box it shouldn't do any harm. Then you only have
> one process that you need to have call tzset when you HUP it for
> instance - to ensure that localtime changes are picked up globally.
Yes, IMHO this is fine idea. Probably I'll try to make it for tests=20
[unfortunately, when i have time :)].
But basically, i meant more deep changes in syslog protocol when timestamp=
information is attached on server side upon syslog entry is received by the=
daemon. This way client isn't involved in timestamp generation at all and a=
a result cannot fabricate it. Even if we consider to send timestamp info in=
UTC format, client still can send invalid information due to software bug o=
doing it explicitly.