It may be a syslog thing now that you mention that. I think I've seen
that before with syslog not noticing some clock changes (mainly TZ
changes) until it's restarted (or maybe SIGHUP also works)
C
On Sun, 2002-03-31 at 20:29, Matthew Dickinson wrote:
>
>
> It took a full stop/start of both s
It took a full stop/start of both spamd and syslog, the restart didn't
seem to hack it..
Thanks for the reply,
Matt
On 31 Mar 2002, Craig Hughes wrote:
> Restart it -- it needs to reopen its connection to syslog to get the new
> time.
>
> C
>
> On Sun, 2002-03-31 at 19:56, Matt Dickinso
Restart it -- it needs to reopen its connection to syslog to get the new
time.
C
On Sun, 2002-03-31 at 19:56, Matt Dickinson wrote:
> Hi,
>
> I'm in england, and following the recent time change from GMT to BST,
> I've noticed that everything on the system seems ok, apart from spamd.
> It still
Hi,
I'm in england, and following the recent time change from GMT to BST,
I've noticed that everything on the system seems ok, apart from spamd.
It still thinks it's GMT, whereas the rest of the system thinks BST.
Below is an extract of my maillog.
Apr 1 04:49:04 tornado ipop3d[30168]: Login us
