Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!hplabs!hpl-opus!hpccc!hp-ses!hpcea!hpausla!brianw
From: brianw@hpausla.HP.COM (Brian Wallis)
Newsgroups: comp.unix.xenix
Subject: SCO(386) 2.3.1 cron & crontab's
Message-ID: <750006@hpausla.HP.COM>
Date: 17 Feb 89 00:00:59 GMT
Organization: HP Australian Software Operation
Lines: 16

Does anyone know of existing problems in SCO(386) 2.3.1's cron. The
problems a friend is having are to do with getting a news feed going
and this involves having cron start a dial program at about midnight.
If the cron entry is set up for 11:00 AM and watched then all is fine.
If it is set to midnight NOTHING happens! Nothing in cron's log, no
dial, no nothing.

He is using the `crontab -r' to delete the existing file and then
`crontab file' to install the new one. Any test which is watched seems
to work, it just all goes away in the wee hours.

Does this ring any bells for anyone out there, my friend is about to
get his sledge hammer and re-adjust his system slightly. It is
difficult for him to hang arround 'till midnight to watch it as the
building is locked up by someone else at 6:00. Anyhow, he is convinced
it would work if he stayed and watched (I am worried about his sanity).