tfb@unf7.UUCP (t blakely) (10/13/90)
We're having problems printing on our single next cube (which resides on an ethernet with suns, sequents and others). Initially I can print one file, any subsequent attempts at printing give "can't start daemon" errors. If I kill and restart lpd, the top file on the queue prints, but it "can't start a daemon" for any others. Any help would be appreciated. Tom Blakely tfb@sinkhole.unf.edu uflorida!unf7!tfb
phd_ivo@gsbacd.uchicago.edu (10/20/90)
Here is another printer problem. My printer daemon apparently spits out the following messages to the console: Oct 10 16:53:08 next npd[111]: found mismatch on printer status, 0x00001110 != 0x00000010 Oct 10 16:53:33 next npd[111]: found mismatch on printer status, 0x00001110 != 0x00000000 Oct 10 16:54:10 next npd[111]: found mismatch on printer status, 0x00000010 != 0x00000000 Oct 10 16:54:36 next npd[111]: found mismatch on printer status, 0x00001110 != 0x00000010 Oct 10 16:54:51 next npd[111]: found mismatch on printer status, 0x00000000 != 0x00000010 Oct 10 16:54:53 next npd[111]: found mismatch on printer status, 0x00000010 != 0x00001110 Is there something broken? The printer seems to work most of the time quite nicely, so is this cause for concern? /ivo welch ivo@next.agsm.ucla.edu