Path: utzoo!attcan!uunet!peregrine!ccicpg!cci632!rit!tropix!moscom!ur-valhalla!uhura.cc.rochester.edu!rochester!udel!mmdf
From: jnall%FSU.BITNET@cornellc.cit.cornell.edu (John Nall 904-644-5241)
Newsgroups: comp.os.minix
Subject: Re**3: Gettin' there with Evans stuff
Message-ID: <17946@louie.udel.EDU>
Date: 22 Jul 89 20:30:18 GMT
Sender: mmdf@udel.EDU
Lines: 27

>> [readclock is bad and prints -q, then date or something crashes]
>>  ...

>  I don't have the problem here.  Please look at it a bit more, since it
>  must depend on your configuration.
>
> Bruce

OK.  I screwed up.  It didn't crash with a little program which only
printed -q and then did an exit(1).  So I went back to a bad version
of readclock and it didn't crash this time!  So after considerable
head scratching I found that I had been using it with a faulty date
call (which I had since fixed).  I had been saying, in /etc/rc:

     /usr/bin/date `readclock`

instead of the correct

     /usr/bin/date `readclock`