jnall%FSU.BITNET@cornellc.cit.cornell.edu (John Nall 904-644-5241) (07/23/89)
>> [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` </dev/tty So if you leave off the </dev/tty in the data call in /etc/rc it should lock up your system. (sorry..."the date call..."). John Nall (p.s. Please excuse my putting this on the network instead of just e-mailing it. I can't seem to get e-mail to you out of here. It keeps sending it back to me).