I were warned but ... now really need your advice
Alma J Wetzker
almaw
Tue May 29 10:14:44 PDT 2007
Vu Pham wrote:
> On Tue, 2007-05-29 at 11:35 -0500, "Michael E. Jaggers" wrote:
>> On Tue May 29, 2007 at 11:24 AM Vu Pham wrote:
>>
>>> On Tue, 2007-05-29 at 11:11 -0500, "Michael E. Jaggers" wrote:
>>>> On Tue May 29, 2007 at 10:50 AM Vu Pham wrote:
>>>>
>>>>> The 9-month old board has worked fine recently. I just found the time
>>>>> problem about two days ago and I thought its battery is dead. Then I got
>>>>> the new board and just want to compare the performance of the two boards
>>>>> and found even the new one has the time problem.
>>>> Since you have multiple systems on your local network, do you have an NTP time source running on one of them?
>>> I am sure npt will help, but my problem is not the time is incorrect; it
>>> is *why* the time is extremely incorrect in the last two days after any
>>> reboot.
>>>
>>> This is a home network.
>> But if you have an NTP server on your local network, it is possible that IT is the one with the bad time. The other machines on the network will simply sync to it. (If that is the way it is configured.) There could be nothing wrong with the others.
>>
>
> Michael, I see your point now. Sorry that I misunderstood it. No, I use
> no NTP at home.
>
> Vu
Still, it is finding a time from somewhere to set the system to. Is the
time change consistent? Is the offset, including minutes, the same each
reboot? Do you have an ntp client active somewhere in the boot process?
You have already investigated the time zone files, could one of them be
corrupted? Have you tried recreating the link in /etc?
Computers, bless them, just don't have the imagination to do something
like that without being told.
-- Alma
More information about the Linux-users
mailing list