[Dovecot] Timezone of logentries from dovecot
Hi
I've been using dovecot for a long time now, and have nothing but praise for it. It's considerably faster than uw-imap, and has been very easy to configure, in spite of my limited knowledge of unix.
One thing still botheres me, though, and that's the time of the entries in my logfiles. It seems that dovecot logs it's entries in GMT, while I'm using GMT+1. This is made even worse by the fact that we're now using daylight savings time, which upps the difference to two hours. Here's a couple of lines from my logs to show the difference:
Apr 29 14:30:07 misterp mach_kernel: ipfw: 10000 Deny UDP 213.122.19.185:33123 129.142.126.35:137 in via en0 Apr 29 14:30:59 misterp mach_kernel: ipfw: 4000 Accept TCP 80.197.22.210:38518 129.142.126.35:995 in via en0 Apr 29 12:30:59 misterp pop3-login: Login: torben [80.197.22.210] Apr 29 14:32:25 misterp mach_kernel: ipfw: 10000 Deny UDP 195.122.208.191:1066 129.142.126.35:1434 in via en0
I don't know how to fix this, whether it's in dovecot or somewhere in a system-setting. However, all other applications log their entries with the systems current setting, so I suspect it's in dovecot. I would very much appreciate any help on the subject.
Btw, I'm using MacOS X 10.2 with dovecot 0.99.10.4.
Thanks!
/Lars
Le Thu, 29 Apr 2004 14:44:35 +0200 Lars Skovgaard a ecrit : [...]
I don't know how to fix this, whether it's in dovecot or somewhere in a system-setting. However, all other applications log their entries with the systems current setting, so I suspect it's in dovecot. I would very much appreciate any help on the subject.
Btw, I'm using MacOS X 10.2 with dovecot 0.99.10.4.
It's because the logging process is chrooted, doesn't have TZ env. var. set, and doesn't have a correct /etc/localtime (or whatever your libc uses) _inside_ the chroot directory. Therefore its timezone is the default, UTC (formerly known as GMT).
-- Quentin Garnier - cube@NetBSD.org The NetBSD Project - http://www.NetBSD.org/
On Thu, 2004-04-29 at 15:48, Quentin Garnier wrote:
It's because the logging process is chrooted, doesn't have TZ env. var. set, and doesn't have a correct /etc/localtime (or whatever your libc uses) _inside_ the chroot directory. Therefore its timezone is the default, UTC (formerly known as GMT).
One more reason to make all logging go through dovecot-master process..
Temporary fix of course is setting login_chroot = no to config file.
participants (3)
-
Lars Skovgaard
-
Quentin Garnier
-
Timo Sirainen