I’ve decided to make an in-home LAN with a router that uses Red Hat Linux 6.3 as its OS. The OS comes with Chronos, a program much like an ‘alarm clock’: It performs certain tasks at specified times. You can set it to perform a task, say, each Wednesday at 0600 or at the first of each month. Chronos is a simple program: It looks at the system time and when the system time is equal to the values it has saved in a vi-modifiable table, it does the deed. That is a problem: I want to use Chronos to modify the system time to account for Daylight Savings Time. When we spring forward, no problem. Chronos modifies the clock and sleeps for another year. When we fall back, I see an infinite recursion waiting to happen. Chronos notices it’s the time to fall back, sets the clock back an hour, sleeps an hour until it notices it’s time to fall back, etc. A rather nasty problem that would completely screw up my system. Are there any solutions? The FM I have is silent on the issue, otherwise I would have RTFM.
Derleth, I don’t know any specifics to give you, but the way I handled things like that in DOS batch files, is to create a file named like “fallback” in your spring forward routine. Then have the fallback routine check for that file name, do it’s thing and then delete it. That way an hour later the file doesn’t exist so it doesn’t execute again.
Hope that gives you an idea how to make it work.
Jim