[rbldnsd] rbldnsd logging in varying timezones ?

Per Jessen per at computer.org
Sun Jun 11 15:22:04 MSD 2006


Michael Tokarev wrote:

> Per Jessen wrote:
>> I've recently upgraded to 996 and noticed that logmessages appear to
>> be logged in two different timezones:
>> 
>> 
>> Jun 10 21:27:26 calcium rbldnsd[31136]: listening on 127.0.0.1/34000
>> Jun 10 21:27:26 calcium rbldnsd[31136]: listening on ::1/34000
>> Jun 10 21:27:26 calcium rbldnsd[31136]: rbldnsd version 0.996 (19 Feb
>> 2006) started (2 socket(s), 16 zone(s)) Jun 10 19:27:27 calcium
>> rbldnsd[31136]: dnset:surbl.org/ws.surbl.org.rbldnsd: 20050204
>> 095615: e/w=82605/0 Jun 10 19:27:27 calcium rbldnsd[31136]:
>> dnset:spamchek.net/list.rbldnsd: 20060207 154729: e/w=272/273
> ....
>> Jun 10 19:27:37 calcium rbldnsd[31136]: zones reloaded, time
>> 10.88e/9.79u sec, mem arena=60800 free=115 mmap=57964 Kb
> []
>> The correct local time for the above is 2127CET, 2 hours ahead of
>> UTC. I have another system running 993, where this problem does not
>> occur.
> 
> Well.  Nothing in that area changed since quite some time (incl. 0.993
> version).

Interesting.  That would indicate it's the base system, not rbldnsd ...
The system where I'm running 993 is using glibc 2.3.2.

> The first messages (up to rbldnsd...started) is logged before
> chrooting. The rest is from chroot jail.
> Upon startup, rbldnsd issues a call tzset() function, which is
> supposed to read local timezone information and use it for all
> subsequent time- related stuff - to work around exactly this issue
> (timezone info not available inside chroot jail).

OK.

> What's your OS? If it's linux (as it seems to be the case from the
> 'zones reloaded' line), what's your glibc version?  The thing is -
> I'm unable to reproduce this problem here... ;)

Yep, it's linux (SUSE 10.1), glibc 2.4.  It's a newly installed vanilla
SUSE 10.1, nothing unusual (I think).  

> Also, how about moving the call to tzset() in rbldnsd.c several lines
> down, right before the line:
> 
>   if (rootdir && (chdir(rootdir) < 0 || chroot(rootdir) < 0))
> 
> ?  Will it rectify the problem?

I'll give it a go.  Thanks for getting back to me so quickly. 


/Per Jessen, Zürich



More information about the rbldnsd mailing list