Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!mips!service!nancy From: nancy@mips.COM (Nancy Louie) Newsgroups: comp.sys.mips Subject: Re: duplicate cron jobs, who is responsible? Message-ID: <39237@mips.mips.COM> Date: 4 Jun 90 16:33:00 GMT References: <39120@mips.mips.COM> Sender: news@mips.COM Reply-To: nancy@mips.COM (Nancy Louie) Organization: MIPS Computer Systems, Inc. Lines: 14 >... stuff deleted ... >This was (note the past tense) Problem Report 5077 (and other duplicates). >It has been fixed for RISC/os 4.50. The problem was a race condition in cron. > Additionally, depending on your support contract, you may be able to call the support line and ask the dispatcher to log a call for you. There is a patched clock script that you can binary reconfig into your kernel that might help you. (Note the use of might. It didn't fix all cases, but the 4.50 os does.) Another thing that you can do is to try to avoid having processes start at or about midnight when the system clock is changed over to the new date. These will help until 4.50 releases.