On Thu, Nov 24, 2005 at 11:48:23PM +0100, Benno Schulenberg wrote:
> Charles Trois wrote:
> > ~ # ls -l /etc/localtime
> > lrwxrwxrwx 1 root root 32 Nov 22 20:39 /etc/localtime ->
> > /usr/share/zoneinfo/Europe/Paris
> >
> > and in /etc/conf.d/clock:
> >
> > CLOCK="local"
>
> Did you maybe chan
Charles Trois wrote:
> ~ # ls -l /etc/localtime
> lrwxrwxrwx 1 root root 32 Nov 22 20:39 /etc/localtime ->
> /usr/share/zoneinfo/Europe/Paris
>
> and in /etc/conf.d/clock:
>
> CLOCK="local"
Did you maybe change this last one after your last reboot? Because
then the system time won't have chan
Benno Schulenberg a écrit :
Charles Trois wrote:
The legal time, here in France and at this (winter) period, is
GMT + 1, as shown correctly by the clock of my iMac, but "date"
keeps returning GMT + 2.
Sounds like your harware clock is running at local time. What does
'hwclock --show --debu
On November 18, 2005 02:14 pm Benno Schulenberg was like:
> Your time zone is correctly set?
> Check with 'ls -l /etc/localtime'.
I think the problem was a corrupt /etc/localtime.
When I set up the system I made /etc/localtime a symlink, but SOMETHING seemed
to have changed that and replaced it
Charles Trois wrote:
> The legal time, here in France and at this (winter) period, is
> GMT + 1, as shown correctly by the clock of my iMac, but "date"
> keeps returning GMT + 2.
Sounds like your harware clock is running at local time. What does
'hwclock --show --debug' say? Look for the line s
On 11/21/05, Charles Trois <[EMAIL PROTECTED]> wrote:
> I too have a clock problem (the time returned by "date" being one hour
> fast), and I have been fiddling with "hwclock" without finding the right
> way. When I saw the above post, I thought that it gave me the answer,
> and tried to apply it,
i am having that same problem also.
On 11/21/05, Charles Trois <[EMAIL PROTECTED]> wrote:
> Benno Schulenberg a écrit :
> I too have a clock problem (the time returned by "date" being one hour
> fast), and I have been fiddling with "hwclock" without finding the right
> way. When I saw the above po
Benno Schulenberg a écrit :
Your hardware clock is supposed to be at UTC?
Check with 'grep CLOCK= /etc/conf.d/clock'.
Your time zone is correctly set?
Check with 'ls -l /etc/localtime'.
If those are okay, do:
rm /etc/adjtime
hwclock --set --utc --date="2005-11-18 21:34" # example time
On Fri, Nov 18, 2005 at 03:57:27PM -0700, Richard Fish wrote:
> Also, the KDE clock has a (IMO a very annoying) "feature" that will
> change the timezone it displays in response to the scroll wheel. So
I never knew of that feature till you just mentioned it. I think
that's pretty cool!
John
--
On 11/18/05, Benno Schulenberg <[EMAIL PROTECTED]> wrote:
> Robert Persson wrote:
> > For instance I sometimes find that the kde clock tells me that I
> > am on UTC rather than PST. At other times it tells me that I am
> > on PST, but gives a time exactly 8 hours in the future.
> >
> > Now it is g
Robert Persson wrote:
> For instance I sometimes find that the kde clock tells me that I
> am on UTC rather than PST. At other times it tells me that I am
> on PST, but gives a time exactly 8 hours in the future.
>
> Now it is getting even weirder because I find that when I boot up
> and enter kde
Another solution if you are having ntpd problems, is to use this command
from a crontab:
ntpdate -b time.nist.gov
stop ntpd before that
On Fri, 18 Nov 2005, Robert Persson wrote:
A week or two back I reset my system clock temporarily to 2001 in order to
install a package under wine with a ti
12 matches
Mail list logo
