Page 1 of 1

Setting the time

Posted: 3. Dec 2010, 17:16
by salparadise
I can't set the time.
Everytime I try to set it via ntp I get an "Cannot authenticate/execute process" message appear.
I've tried "clocksetup" - no joy, 'kcontrol" doesn't exist.

I'm at a loss.
The laptop is 15 minutes slow.

Any solutions?

Thanks.

Re: Setting the time

Posted: 3. Dec 2010, 21:21
by gapan
Is there a chance you picked the wrong timezone when installing salix?
ntp should be working out of the box, so no need to do anything to set
it up. As a last resort you could disable ntp and set the clock manually
with clocksetup or gtkclocksetup.

Re: Setting the time

Posted: 4. Dec 2010, 00:49
by thenktor
Wrong timezone should not give any errors, it should just give you wrong time. Please post the output of "ntpq -p" (run it as root). If ntpd is not running you can start it as root with "service start ntpd".

Re: Setting the time

Posted: 4. Dec 2010, 07:50
by salparadise
Thanks for the reply.
The problem appears to have cleared, I'm just not sure how.

I restarted rc.ntpd and also ran a command I found online (netdate time-a.nist.gov).
Even though I'm in the UK, the time suddenly went from being 15 minutes out, to correct.

My timezone is still wrong and I cannot reset it - I get the same "Cannot authenticate/execute process" message that I got when trying to tell KDE to use online time syncing.

I set the correct timezone when installing.

I am also having trouble setting the time.

Posted: 10. Apr 2011, 22:23
by pokey
I was also having trouble getting the time set correctly. I'm sure I set the timezone right during install, and I have verified that it was set correctly while the time was wrong, is set right now.

While the clock was wrong output from ntpq -p is as follows:

Code: Select all

root[p]# ntpq -p
No association ID's returned
The following seems to have fixed it for me:

Code: Select all

su
service stop ntpd
service start ntpd -Ag
service stop ntpd
service start ntpd
I have no idea what I'm doing, I was just poking at commands as root, because that seemed like the right thing to do. :P

cheers!

If what I did was really bad, go ahead and say so, so that others don't blindly follow the blind into chaos.