> Hey,
> Ben Sunshine-Hill found the problem. My hardware clock was simply
> off by 5 hours. I should be 5 hours behind GMT, but my hardware clock was
> reporting itself to be 10 hours behind GMT. Not sure how that happened
> ("date" was reporting the correct timezone --CDT). I reset the
> Hey,
> Ben Sunshine-Hill found the problem. My hardware clock was simply
> off by 5 hours. I should be 5 hours behind GMT, but my hardware clock was
> reporting itself to be 10 hours behind GMT. Not sure how that happened
> ("date" was reporting the correct timezone --CDT). I reset the
--- "Bryan K. Walton" <[EMAIL PROTECTED]> wrote:
> Hi Ben,
> I implemented this, thanks for the details. I
> assume this is
> reversed, and that suspend.d/time.sh should really
> read
> /usr/sbin/hwclock --systohc --utc
> and that resume.d/time.sh should really read
> /usr/sbin/hwclock --h
--- "Bryan K. Walton" <[EMAIL PROTECTED]> wrote:
> Hi Ben,
> I implemented this, thanks for the details. I
> assume this is
> reversed, and that suspend.d/time.sh should really
> read
> /usr/sbin/hwclock --systohc --utc
> and that resume.d/time.sh should really read
> /usr/sbin/hwclock --
> As for APM suspend and
> resume, Ben says I need a script in /etc/apm/ that
> runs "hwclock --systohc
> --utc" in a script in suspend.d/, and "hwclock
> --hctosys --utc" in
> resume.d/. Don't know how to compose such a script
> though. Any advice?
>
Here's my thingy.
---/etc/apm/suspend.d/
if it only has to run those commands just make to files:
one called hwsync-susp and the other hwsync-resume
put the line
#!/bin/sh
at the top and the hwclock line below it in the file were you want it
respectively
then a chmod +x
Now I take it there are two directories, one for suspend-scripts and
> As for APM suspend and
> resume, Ben says I need a script in /etc/apm/ that
> runs "hwclock --systohc
> --utc" in a script in suspend.d/, and "hwclock
> --hctosys --utc" in
> resume.d/. Don't know how to compose such a script
> though. Any advice?
>
Here's my thingy.
---/etc/apm/suspend.d
Hey,
Ben Sunshine-Hill found the problem. My hardware clock was simply
off by 5 hours. I should be 5 hours behind GMT, but my hardware clock was
reporting itself to be 10 hours behind GMT. Not sure how that happened
("date" was reporting the correct timezone --CDT). I reset the hardware
if it only has to run those commands just make to files:
one called hwsync-susp and the other hwsync-resume
put the line
#!/bin/sh
at the top and the hwclock line below it in the file were you want it
respectively
then a chmod +x
Now I take it there are two directories, one for suspend-scripts an
> Greetings!
> I think I have finally managed to get Debian working correctly
> with APM (suspend/resume features) on my IBM Thinkpad. On boot up, my
> laptop sets the time from a NTP server on the Internet using
> ntpdate. However, after coming out of suspend mode, the time is always
>
Hey,
Ben Sunshine-Hill found the problem. My hardware clock was simply
off by 5 hours. I should be 5 hours behind GMT, but my hardware clock was
reporting itself to be 10 hours behind GMT. Not sure how that happened
("date" was reporting the correct timezone --CDT). I reset the hardwar
> Greetings!
> I think I have finally managed to get Debian working correctly
> with APM (suspend/resume features) on my IBM Thinkpad. On boot up, my
> laptop sets the time from a NTP server on the Internet using
> ntpdate. However, after coming out of suspend mode, the time is always
>
Greetings!
I think I have finally managed to get Debian working correctly
with APM (suspend/resume features) on my IBM Thinkpad. On boot up, my
laptop sets the time from a NTP server on the Internet using
ntpdate. However, after coming out of suspend mode, the time is always
behind by
Greetings!
I think I have finally managed to get Debian working correctly
with APM (suspend/resume features) on my IBM Thinkpad. On boot up, my
laptop sets the time from a NTP server on the Internet using
ntpdate. However, after coming out of suspend mode, the time is always
behind by
14 matches
Mail list logo
