[syslog-ng]ISODATE offset?

[Dave Johnson]

scott--  

We had some timezone issues awhile back...  So I thought I could help
here, but now it appears you have a different problem, so all I can
offer is outside advice:

* Do you have a local environmental variable in your user account for TZ?
* Balazs may know better, but maybe you could force the function 
   "length = strftime(dest, left -1, "%z", tm);"  as opposed to      
   HAVE_GLOBAL_TIMEZONE...  in the timezone checking part of the code above?
   - You can check in your config.log if this was set... ?  On my relatively up
     to date gentoo box it was set.

On Fri, 12 Nov 2004 16:18:40 +1000, scott <syslogng@slittle.com> wrote:
> >>>Hmm.. your system-wide timezone setting might have problems. what
> >>>platform are you using?
> 
> >>Debian Linux; one Testing (syslog-ng v1.6.4-1), one Unstable (syslog-ng
> >>v1.6.4-2).
> 
>  >What version of glibc?   What is your local timezone set to?
> 
> 
> libc6          2.3.2.ds1-18   GNU C Library: Shared libraries and Timezone
> 
> /etc/timezone is Australia/Sydney.  +1000 is standard time, but we're
> now in DST, so it should be +1100.
> 
> The only workaround would be to log a plain Unix timestamp and convert
> later, but there doesn't seem to be a macro for that...
> _______________________________________________
> 
> 
> syslog-ng maillist  -  syslog-ng@lists.balabit.hu
> https://lists.balabit.hu/mailman/listinfo/syslog-ng
> Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
> 
>