Daylight savings time

[utu]

.
On 11/6/11, my Knoppix 6.7.1 LiveUSB seemed to require adding ntpdate to provide
the correct transition from daylight-savings to standard time via internet access to NTP.

The other settings which without ntpdate seemed all right for Eastern US time until
this Sunday were as follows:

My hardware clock is set to local time; in /etc/default/rcS, 'UTC=no' is set; and in
/mnt-system/boot/syslinux/syslinux.conf, kernel option is set to 'tz=America/New_York'.

I've not changed any of these settings, only added ntpdate via Synaptic.

I think I've found that booting up Windows 7 on the same computer after the time change
has occurred has the same effect, without requiring the addition of ntpdate.

[Werner P. Schulz]

I've not changed any of these settings, only added ntpdate via Synaptic.
Only installing ntpdate via synaptic is of no use.
You have to run ntpdate either manually or in a cron-job. And it is very important, which parameter you use for ntpdate.

In an earlier posting I mentioned, you will run in trouble with dualboot installation of Linux and Windows, if your BIOS clock isn't UTC.

[utu]

Hi, Werner.
Nice to hear from you.

I was and am surprised at how compatible ntpdate is with Windows 7
with the configuration I have described.

If I were dual booting more often,
I might have imagined that ntpdate was unnecessary.

As it is the effective appearance is:
If Windows has 'updated the hardware clock', ntpdate does nothing;
If Windows hasn't 'updated the hardware clock', then ntpdate does so.

I know the Linux standard is UTC. I still prefer local time.
I think I now have identified all the pieces that go together
to make that happen consistently.

[Werner P. Schulz]

Which parameter do you use with "ntpdate" and how do you start it:
manually or via cron-job?

[utu]

Hi, Werner.
I have just accepted the default /etc/default/ntpdate, which is:



# The settings in this file are used by the program ntpdate-debian, but not
# by the upstream program ntpdate.

# Set to "yes" to take the server list from /etc/ntp.conf, from package ntp,
# so you only have to keep it in one place.
NTPDATE_USE_NTP_CONF=yes

# List of NTP servers to use (Separate multiple servers with spaces.)
# Not used if NTPDATE_USE_NTP_CONF is yes.
NTPSERVERS="0.debian.pool.ntp.org 1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org"

# Additional options to pass to ntpdate
NTPOPTIONS=""
It may be noted that there is no file /etc/ntp.conf in my /etc.

knoppix@Microknoppix:~$ less /etc/services | grep ntp
nntp 119/tcp readnews untp # USENET News Transfer Protocol
ntp 123/tcp
ntp 123/udp # Network Time Protocol
nntps 563/tcp snntp # NNTP over SSL
nntps 563/udp snntp
knoppix@Microknoppix:~$

Also, I do NOT also have ntp itself installed.

[utu]

ps: Werner, this may be what you are looking for:

/var/log/dpkg/info/ntpdate.conffiles:
/etc/network/if-up.d/ntpdate
/etc/logcheck/ignore.d.server/ntpdate
/etc/dhcp/dhclient-exit-hooks.d/ntpdate
/etc/default/ntpdate

There is indeed an executable file ntpdate in /etc/if-up.d,
and that's the way it seems to work: within one minute of
getting wifi on-line, a time correction is made.

[utu]

I was having this usual problem of mine also setting up Mint 11 LXDE,

To cure the local time problem, per Mint forum:
sudo apt-get install gnome-time-admin, then
System Tools>Time>Zone>America/New_York, in my case.

This works on Mint 11; it's worth a try here.

[utu]

ps
I've tried this via Synaptic and concluded that Knoppix
doesn't have enough gnome infrastructure to run gnome-time-admin, unfortunately.