Log in

No account? Create an account

Previous | Next

Linux hubris

So I sat back and laughed as everyone struggled to get their PC's adjusted to the earlier onset of Daylight Saving Time. But I was apparently being a hypocrite, because I noticed my Linux machine's clock still on CST today! The problem turned out to be that the DST patch had been applied to the zoneinfo files, but never copied to the /etc/localtime file which is what the system uses to determine its own timezone. Simply copying the file fixed the problem (I didn't even have to reboot!) but still... one can't be too careful.


( 8 comments — Comment )
Mar. 14th, 2007 04:11 am (UTC)
Thank you for pointing me in the right direction of how to fix it on killfile. I feel better to know that I wasn't alone in this.

Mar. 14th, 2007 02:34 pm (UTC)
Glad I helped. And now I am feeling less like an idiot myself. :)
Mar. 14th, 2007 03:24 pm (UTC)
Oh and... according to what I've been reading, /etc/localtime is SUPPOSED TO BE or TYPICALLY a symlink back to the "right" zoneinfo file for the machine's timezone. But on all our systems, it's actually just a separate copy of the file. Somewhere the install and the patch logic got out of sync; the patches just patch the zoneinfo files assuming that the /etc/localtime file will just follow as a symlink, except that's not how things were actually installed or initially set up.
Mar. 14th, 2007 04:52 pm (UTC)
a copy? ugh, lame.
Mar. 14th, 2007 11:31 am (UTC)
People were struggling? With their PC's? I didn't have to do anything on my new laptop and at work I had to, um, turn the clock forward one hour.

The biggest struggle I had was trying to keep someone in our IT department from updating lots of software on one of our machines, thus costing us $$ we don't have for this fiscal year, because he was freaking out about DST. When I understood that the ramifications would mean manually setting the clock forward, I was sufficiently amused.
Mar. 14th, 2007 02:31 pm (UTC)
Well, sure, one can trivially set their clock forward, but typically a machine is running time-synchronization software which operates in UTC. So it's important to have the offset from UTC set correctly in a machine. You could always set your machine's timezone to Eastern Time for these three weeks, but then any email you send is going to have an incorrect Date.

While I agree that people are freaking out about this out of proportion to the actual severity of the issue, but it's a little oversimplistic to point and laugh and say "dude just chill and set your clock ahead."
Mar. 14th, 2007 02:44 pm (UTC)
Dude, this is what you respond to?

Mar. 14th, 2007 02:46 pm (UTC)
My attention span is very short these days.
( 8 comments — Comment )



Latest Month

July 2013