[rbldnsd] rbldnsd logging in varying timezones ?

[Per Jessen]

Michael Tokarev wrote:

> Really nothing has changed in rbldnsd in this area, for a very
> long time.  The whole time stuff is the only one I know -- call
> tzset() before chroot(), to force time-related libc functions
> to read/parse current timezone information into memory, so that
> no access to timezone data will be required.  Glibc (and - I
> think - other libcs) does not provide anything else for that
> purpose, and a call to tzset() is the one to do in such a
> situation (when chrooting).

Sounds reasonable, yes.

> Is it something specific to your single machine, or does any
> suse linux machine behaves this way?  I can definitely say
> that, for example, on debian and redhat, many versions, it
> works correctly.  Also on several versions of solaris and
> freebsd...

I'll check if anyoneelse has seen this.

> In any way, the problem is NOT in rbldnsd.  It's in glibc.
> The sequence:
> 
>   tzset()
>   chroot(...)
>   do_something_timezone-related()
> 
> is the real and only way to ensure we will not access non-
> existing timezone information after chrooting().  This is
> portable.  So if in your case this standard sequence does
> not work, and the only other piece of software involved is
> glibc, it must be a bug in glibc somewhere.

Which sounds like it should be easy and straightforward to reproduce?



/Per Jessen, Zürich