Resetting clock local time.

[Werner P. Schulz]

I might still have a problem when we hit Daylight Savings time, ...

If you follow my description, you'll always have the correct time. The time is calculated by the instructions you can see in the files of '/usr/share/zoneinfo/'.

[E-Tramp]

Well, I will read up on it and see what you are talking about. Thanks for all of the help. I still have a lot to learn, so, and time to learn it. Wish I had more time to spend reading this stuff, but, I have to do other things too. I really haven't figured out the Micro Re-Mastering, but, I suppose I will eventually. I will be posting other issues as well.

[rajibando]

The process I am trying to implement is the most logical and generalised one, so please suggest something along the line.

[Werner P. Schulz]

The UNIX/ LINUX way is:

• always BIOS time = UTC

With Debian I use the crontab:

40      10,15,20        * * *   /usr/sbin/ntpdate -v de.pool.ntp.org; /sbin/hwclock -u --systohc

With dual boot Windows installation you have to register:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\↲
    Services\W32Time\TimeProviders\NtpClient]
"SpecialPollInterval"=dword:00000e10

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\↲
    CurrentVersion\DateTime\Servers]
@="1"
"1"="de.pool.ntp.org"
"2"="time.nist.gov"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\↲
    TimeZoneInformation]
"RealTimeIsUniversal"=dword:00000001

[rajibando]

Why configure crontab? My system automatically updates the time when I log in to the internet. The ntpdate client listens to the network time servers by itself.
I don't use windoze, so I would not be interested in its registry codes.
Okay, this is one thing that we have got to look into in Knoppix.
But that the BIOS is updated by ntpdate is absolutely confirmed. In doze, if you change time the BIOS time is affected too.

[Werner P. Schulz]

Why configure crontab?

Why not?

But that the BIOS is updated by ntpdate is absolutely confirmed.

Why do you think so? From man ntpdate:

ntpdate sets the local date and time by polling the Network Time Protocol (NTP) server(s) given as the server arguments to determine the correct time.

[rajibando]

Why not?Why do you think so? From man ntpdate:

Because I have seen that happening with my BIOS Let us not be hasty. We can solve this issue universally if we think hard.

[rajibando]

Because I have seen that happening with my BIOS Let us not be hasty. We can solve this issue universally if we think hard.

I am sorry, I should have been more elaborate. Actually, I have a localised system, as explained earlier. ntpdate sends that process the ntp data( time and date), and it localises the date time according to my settings(Asia/Kolkata) and rewrites the BIOS on that basis.

[utu]

.
I have a nice Dell laptop which came equipped with Windows 7.
I rarely use Windows 7, but it allows the laptop to be very close
to 'Observatory time' since it syncs up my hardware clock with an
ntp server every time it IS used. I also corrects for daylight
savings time, if allowed a peek at the internet. The hardware
clock in question is set to local Eastern US time. I also set
my Knoppix desktop to local 12-hour am/pm format.

I don't use ntpdate or any other Knoppix time correction.
The consequences of this are two as far as I can tell.
1. The result of a date command will erroneously append UTC to
the otherwise very nearly correct local time.
2. There is a small error, currently about 15 seconds, which I
observe by occasionally checking against the USNO.
See: http://tycho.usno.navy.mil/simpletime.html.

If I wanted to tweak the small error, I could spend a few
minutes with Window 7.
If I wanted to tweak the erroneous UTC, I could use an alias
date="date | sed 's\UTC\EST\'" or date="date | sed 's\UTC\EDT\'"

I rarely find the need to do either.
Nor do I care to disturb my Windows 7 which works ok for what it is.

[Werner P. Schulz]

Please tell us the output from

cat /proc/driver/rtc; date

1. from Debian
2. from Knoppix

My values are with Debian

rtc_time    : 07:38:25
rtc_date    : 2013-01-28
alrm_time    : 00:00:00
alrm_date    : ****-**-**
alarm_IRQ    : no
alrm_pending    : no
24hr        : yes
periodic_IRQ    : no
update_IRQ    : no
HPET_emulated    : yes
DST_enable    : no
periodic_freq    : 1024
batt_status    : okay
Mo 28. Jan 08:38:25 CET 2013

with Knoppix

 cat /proc/driver/rtc; date
rtc_time    : 07:41:11
rtc_date    : 2013-01-28
alrm_time    : 00:00:00
alrm_date    : 2013-01-29
alarm_IRQ    : no
alrm_pending    : no
update IRQ enabled    : no
periodic IRQ enabled    : no
periodic IRQ frequency    : 1024
max user IRQ frequency    : 64
24hr        : yes
periodic_IRQ    : no
update_IRQ    : no
HPET_emulated    : no
BCD        : yes
DST_enable    : no
periodic_freq    : 1024
batt_status    : okay
Mon Jan 28 08:41:11 CET 2013

Timezone for me is "Europe/Berlin"