Looks like this is working now. An earlier post pointed out that the time.nist.gov server seemed to be down over the weekend. I guess that was my problem. It is working now. Thanks to all who replied. Bill Johnson "Jesus could have saved Himself from the cross, but then He wouldn't have saved me." (Rick Warren) On Mon, 5 Apr 2004, Dexter Ang wrote: > On Mon, 2004-04-05 at 18:58, Bill Johnson wrote: > > I searched, but didn't see an answer to this. I have always used rdate to > > keep my system clock in sync with time.nist.gov NTP time server. When > > daylight savings time hit this past weekend, I noticed that the time on my > > laptop did not change. I tried to do it manually, with no affect. Is > > there a problem with rdate under fedora? > > > > If I run rdate -s time.nist.gov, I get a message displayed: > > > > Alarm clock > > > > but no change to the system time. I have also tried other NTP servers > > with the exact same result. I get the same result if I try rdate -p > > time.nist.gov (or any other NTP server). > > > > Any suggestions? I miss the assurance of my laptop time being accurate. > > There was already a thread asking about the "Alarm clock" return value. > Unfortunately, no one seems to know since no one's answering. All I can > recommend to you is to do what I do... try other NTP servers. I usually > use time.nrc.ca and results are normally good. You might want to try > that server. Good luck! > > dex > > > -- > fedora-list mailing list > fedora-list@xxxxxxxxxx > To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list >
