Re: Cron misbehave...

From: jack (not@all.org)
Date: 02/23/03

  • Next message: jack: "Re: Cron misbehave..." 
    From: jack <not@all.org>
Date: Sun, 23 Feb 2003 12:05:01 +0100

    Kasper Dupont wrote:
    > Are you setting the clock from crontab? That is usually a bad idea.

    Mmmh, I know now... - But I don't see why this would "usually" be
    a bad idea... - Any hints...? - It worked well and does work well,
    as long as that radio device reads the time correctly...

    > It would probably be better to use ntpd.

    Very true... - I'm setting that one up right now.

    I'm not too sure, but the ntp suite does support this device called
    "pcf". How would ntpd behave when it gets a corrupted time from that
    thing? - As said, the program that is available, also called "pcf",
    is quite simple and hence, stable. I just added this "sanity check"
    to see whether the radio clock reports a time that is more than 2h,
    = 7200s, away, and if it is, does omit adjusting the system time.

    But, again, even if I do all troubleshooting to avoid this, the
    question is why cron fails after a major time leap...

    Cheers, Jack. 

    -- 
----------------------------------------------------------------------
My personal reading of the string "MicroSoft" expands to "NanoWeak"...