Can't set clock

[O. Sinclair]

Derek Broughton wrote:
> David Fletcher wrote:
> 
>> On Sunday 04 Jan 2009, Wulfy wrote:
>>> I have ntpdate installed.  I think that supplies the daemon.
>>>
>>> <sigh> I've had problems with the public time servers ever since I moved
>>> to Linux when Sarge was Testing in Debian.  I've never had a problem
>>> like this, though.
>>>
>> I've never installed ntpdate. I didn't know there was such a thing.
> 
> Please don't give users advice like this when you don't even know what the 
> default-installed software does.
> 
> ntpdate is the default installed by ubuntu because most of us don't need a 
> time server.
> 
> I'd recommend  you just look at syslog when you run ntpdate - it will 
> usually tell you why it didn't work (and it usually means you have an 
> invalid time server - which wouldn't be solved by installing ntpd)
> 
>> What I'd try is removing ntpdate then install ntp (or is it ntpd? I can't
>> recall). If it needs ntpdate it should put it back.
> 
> It probably _won't_ need ntpdate if you have ntpd, but I really don't like 
> the idea of users, who can't even figure out why ntpdate isn't working, 
> running time servers.
>> Then what happens is, your system will not immediately show the correct
>> time, it will very gradually adjust itself little by little. Unless you
>> reboot it, then I think it sets itself correctly right away.
> 
> 
> 
I managed by typing:
sudo ntpdate oceania.pool.ntp.org
and that is also the timeserver I have set the "systray" clock to use

Sinclair