Path: utzoo!utgpu!attcan!uunet!husc6!bbn!rochester!rutgers!tut.cis.ohio-state.edu!cwjcc!hal!nic.MR.NET!tank!mimsy!haven!purdue!decwrl!hplabs!hpda!hpcuhb!hpsmtc1!markc
From: markc@hpsmtc1.HP.COM (Mark Corscadden)
Newsgroups: comp.unix.xenix
Subject: Re: interesting "feature" in 2.3.1
Message-ID: <13280002@hpsmtc1.HP.COM>
Date: 1 Nov 88 22:48:43 GMT
References: <2465@turnkey.TCC.COM>
Organization: Hewlett Packard, Cupertino
Lines: 20

> / hpsmtc1:comp.unix.xenix / sandy@turnkey.TCC.COM (Sanford 'Sandy' Zelkovitz) /  4:33 pm  Oct 31, 1988 /
> I noticed a very interesting "FEATURE" in version 2.3.1 of Xenix386. This
> has to do with the time change last Sunday. All worked perfectly as the clock
> was reduced by one hour at 2AM. The interesting "feature" was that I have many
> crontab entries and during the day, on Sunday, each entry was executed TWICE!
> Each entry was executed one hour earlier than it was supposed to do so and
> then at the correct time! I rebooted the system and this "feature" no longer
> existed! It seems that cron may have a small problem.
> 
> Sanford <sandy> Zelkovitz
> ----------

This must be a cron problem that evolved early - I have seen exactly the
same problem running HP-UX, which is Hewlett-Packard's version of UN*X. I
don't know how far back you need to go in order to find a common ancestor
of HP-UX and version 2.3.1 of Xenix386, but I'm guessing they may both have
inherited this bug from a common 'source'.

Mark Corscadden			| don't want a pickle,
hplabs!hpda!markc		| jest want to ride my moter-cickle