[bitfolk] Bitfolk's spamassassin service configuration

Top Page

Reply to this message
Author: Richard King
Date:  
To: users
Old-Topics: Re: [bitfolk] Squeeze - cannot access the hardware clock by any known method
New-Topics: Re: [bitfolk] Squeeze - cannot access the hardware clock by any known method
Subject: [bitfolk] Bitfolk's spamassassin service configuration
Sorry Andy, you must get fed up with rather naive questions here. Having
had Dovecot problems before with jumps in time knocking dovecot over, I
wanted to make sure everything was going OK with time. Obviously on my
Debian box at home, I make sure hardware clock is synched. But even more
obviously several VPS on a single machine could not keep fiddling with a
hardware clock. The result would be like my mind - complete and utter chaos.

ntpd is working perfectly as running ntpq -p showed, and it is talking to
the proper servers. Thanks so much for the rapid reply and I apologise for
the simplistic question - put it down to the fact that I reached 63 this
week.

Keith

On 12 May 2012 23:18, Andy Smith <andy@???> wrote:

> Hi Keith,
>
> On Sat, May 12, 2012 at 11:09:57PM +0100, Keith Williams wrote:
> > Have just installed Squeeze on a vps (twice! had problems first time
> round)
> > Everything looks good and is ready for me to start installing the web
> sites
> > etc, but I can't get ntpd running as I get the message in the subject.
>
> Have you actually checked that ntpd is not running? The reason I ask
> is that this is not a message output by ntpd but from hwclock, and
> is harmless. VPSes don't have hardware clocks.
>
> > I have tried running hwclock --d