[Ilugc] Re: [OT] Dreaded Deep Blue Screen... Time setting
lug at chandrashekar.info
Sun Oct 31 12:51:54 IST 2004
Ramanraj K writes:
> A little OT but:
> I posted about the "Dreaded Deep Blue Screen" at about 8:40 AM but
> Chandrashekar Babu replied to that by 7:20 AM ? Did the monsoon blues
> eat up some clock ticks as well?
The problem has actually got to do with my machine's time settings. When I
boot into FreeBSD and then reboot back onto Linux, I lose 5:30 hours. Oh
well, on both OS, I've set my timezone to Asia/Calcutta (Asia/India) or IST,
respectively. I'm a bit clueless about what might have gone wrong. Infact,
I'm facing this issue across different Linux distros setup in multiboot
configuration too, lately [Slackware 10.0 with Mandrake 10.1 CE, for
Maybe I must add 'ntpdate' in my system startup scripts.
> I noticed that my sys clock lost 2 hrs
> yesterday, and I reset the time.
In some cases, this could also be caused due to a faulty (or inaccurate) RTC
chip on your system motherboard.
> BTW, should'nt GNU Mailman be stamping
> time on mails to prevent ante-dated postings?
I dont know if thats a good idea. Though in a typical postal mailing
system, the postal service would stamp date and time(?) seal _on_ the cover
of the letter, they cannot or should not change the date and time stamp of
the letter which is _in_ the cover (which is set by the sender). I guess its
a similar analogy in here too.
Another good reason that I could think of: It lets us figure the time when
someone sent an email from _his_ location. Now, if that person resided
in the US, and GNU mailman was setup here in India (following a different
timezone of course) and is configured to modify date/time stamp of all
email that it forwards, the whole purpose would be defeated.
It also reminds me to keep my system time in sync, when
someone identifies a bogus time stamp on my email ;-)
More information about the ilugc