On 05/31/2011 07:42 PM, Sam Varshavchik wrote:
> Tom Horsley writes:
>
>> On Tue, 31 May 2011 16:26:21 -0400
>> Sam Varshavchik wrote:
>>
>> > Before I begin a long and painful adventure in pulling apart with
>> what's
>> > happening with systemd/initscripts, anyone has any clues where I
>> should
On Tue, 2011-05-31 at 17:00 -0400, Sam Varshavchik wrote:
> the laptop's been on the mains power all the time, and wouldn't be
> drawing the CMOS battery at all.
Depends on the circuit design. It's quite possible for part, or all, of
the BIOS to depend entirely on a battery.
--
[tim@localhost
On Tue, 2011-05-31 at 16:26 -0400, Sam Varshavchik wrote:
> On my laptop, it seems that at every boot the clock is offseted by my
> timezone.
>
> Date/Time properties shows "System clock uses UTC" unchecked. This is a dual-
> boot with WinXP, so I must keep the bios clock on local time. Yet, it
Tom Horsley writes:
On Tue, 31 May 2011 16:26:21 -0400
Sam Varshavchik wrote:
> Before I begin a long and painful adventure in pulling apart with what's
> happening with systemd/initscripts, anyone has any clues where I should
look?
Check /etc/adjtime, it should say LOCAL, not UTC. You can
On Tue, 31 May 2011 16:26:21 -0400
Sam Varshavchik wrote:
> Before I begin a long and painful adventure in pulling apart with what's
> happening with systemd/initscripts, anyone has any clues where I should look?
Check /etc/adjtime, it should say LOCAL, not UTC. You can also run
hwclock --local
On 05/31/2011 02:00 PM, Sam Varshavchik wrote:
>
> It would be rather strange if a low cmos battery would result in the
> hardware clock being slow exactly by exactly four hours,
It would indeed, which is why I pointed out that it's probably not an
issue here. I would like to point out, however,
Joe Zeff writes:
On 05/31/2011 01:26 PM, Sam Varshavchik wrote:
> Before I begin a long and painful adventure in pulling apart with what's
> happening with systemd/initscripts, anyone has any clues where I should
> look?
The next few times you boot, go into your BIOS and make sure the time's
ri
On 05/31/2011 01:26 PM, Sam Varshavchik wrote:
> Before I begin a long and painful adventure in pulling apart with what's
> happening with systemd/initscripts, anyone has any clues where I should
> look?
The next few times you boot, go into your BIOS and make sure the time's
right there. And, if