> My Slackware systems which were running at the exact time of the
> wintertime switch were automatically updated but the systems which were
> offline during the switch did not update themselves automatically after
> they were turned on.
>
> - dfisek

Yes, my assumption is that unlike MSWIN, UN*X's do not know about a
time change unless they are running. Is this assumption correct?

By the way, is it the kernel that keeps checking for a Summertime
to Wintertime change? There is no daemon running that monitors this as
far as I know.

Thx.

On 2006-10-30, Manimoto <manimotomushi@hotmail.com> wrote:
> I did an upgrade from 10.2 -> 11.0, i.e. did not do a complete
> reinstall.
> Everything went well, and the system is running with no problems.
> However two days ago when Ontario, Canada switched from summer time,
> the time was not automatically updated on the pc.
> THX
>

I didn't notice until your post. I used the KDE clock 'Adjust time and
date' function and clicked on the 'set time and date automatically'
checkbox. The clock changed. Maybe a minor oversight...

On 30 Oct 2006 18:28:24 -0800, "Manimoto" <manimotomushi@hotmail.com> wrote:

>By the way, is it the kernel that keeps checking for a Summertime
>to Wintertime change? There is no daemon running that monitors this as
>far as I know.

ntpd, use ntpdate prior to running ntpd to jump to correct time.

Grant.
--
http://bugsplatter.mine.nu/

Manimoto wrote:

> By the way, is it the kernel that keeps checking for a Summertime to
> Wintertime change? There is no daemon running that monitors this as
> far as I know.

The kernel maintains system time in UTC, which has no concept of
daylight-savings time. The conversion to local time, with or without
daylight-savings, is done in user-space by the programs that read and
display the system time. That's the whole point of /etc/localtime.

--
----------------------------------------------------------------------
Sylvain Robitaille syl@alcor.concordia.ca

Systems and Network analyst Concordia University
Instructional & Information Technology Montreal, Quebec, Canada
----------------------------------------------------------------------

Manimoto wrote:
> Anyone have a clue how to fix this?

create a file in /etc/cron.hourly/ called updatetime
with +x permission and put into this:

#!/bin/sh
echo "Updating time" | logger
/usr/sbin/ntpdate pool.ntp.org | logger
/sbin/hwclock --systohc | logger


--
Davide Consonni
<davideconsonni@virgilio.it>
http://csvtosql.sourceforge.net

On 2006-10-31, Davide Consonni <davideconsonni@virgilio.it> wrote:
> Manimoto wrote:
>> Anyone have a clue how to fix this?
>
> create a file in /etc/cron.hourly/ called updatetime
> with +x permission and put into this:
>
> #!/bin/sh
> echo "Updating time" | logger
> /usr/sbin/ntpdate pool.ntp.org | logger
> /sbin/hwclock --systohc | logger


Why? That's the purpose of ntpd.

--

http://rlworkman.net

Davide Consonni wrote:

> create a file in /etc/cron.hourly/ called updatetime ...

Strikes me as a hack (an ugly hack, even), rather than a fix ...
It might "work", but it certainly doesn't fix the underlying problem.

To the OP, at the risk of pointing out something obvious and already
checked, check the permissions of /usr/share/zoneinfo and below. Files
should be world-readable, and directories should be readable and
executable for all users.

--
----------------------------------------------------------------------
Sylvain Robitaille syl@alcor.concordia.ca

Systems and Network analyst Concordia University
Instructional & Information Technology Montreal, Quebec, Canada
----------------------------------------------------------------------

Barnacle Bill wrote:
> I didn't notice until your post. I used the KDE clock 'Adjust time and
> date' function and clicked on the 'set time and date automatically'
> checkbox.

Which uses the NTP server shown in dropdown list on right side of it.
So, it doesn't work without Internet connection.


--
Milan Babuskov
http://njam.sourceforge.net
http://swoes.blogspot.com

Sylvain Robitaille wrote:
>
> The kernel maintains system time in UTC, which has no concept of
> daylight-savings time. The conversion to local time, with or without
> daylight-savings, is done in user-space by the programs that read and
> display the system time. That's the whole point of /etc/localtime.

Ok thanks. Just what does /etc/localtime or /etc/ localtime-copied-from
do?

How does the time change occur automatically? What program was
responsible for
changing the time on my PC 3 days ago when it went from Oct 29, 02:00
daylight saving time
to Oct 29, 01:00?

As to user-space, there are progs like tzfile, tzname, tzselect, tzset,
etc.
I don't see any of these being used in any slackware scripts - only
hwclock is used.
Also there just are no "time related" daemons running which could be
responsible for
auto time changing.

You seem to be a sys admin - right? Hope you can answer these mind
bending questions :-)

On Mon, 30 Oct 2006 18:28:24 -0800, Manimoto wrote:

> Yes, my assumption is that unlike MSWIN, UN*X's do not know about a time
> change unless they are running. Is this assumption correct?

Not in my experience. This PC (set to UTC because it has no MS OS
installed) had the new correct time when I turned it on Sunday morning. I
don't use ntpd to keep the time set, but I do occasionally run ntpdate
when I'm connected to the Internet.

Now, when I get back to my dual-boot PC (set to local time to keep Win98
happy), I'll try to remember to run Windows first so it can handle the
time change. I read somewhere that that's the recommended action to take,
and it resets that PC just once, so perhaps Linux won't change the time on
a PC set to local time instead of UTC. That's just a guess that explains
my experiences.

--
Chick Tower

For e-mail: aols . sent . towerboy AT xoxy . net