Sometimes, printers give the code that they are off-line (ran out of ink, someone physically took it off line), or the "I'm OK and ready to do your bidding, master" signal doesn't get recieved, so lpd thinks that the printer isn't working. You should be able to see this with lpc status, and a quick way to fix it is with lpc up all.
Nick Cook wrote: > I recently had a sudden "ain't going to print" problem (although not on a > network), and I got around it by dropping into root and going to "lpc". > Then I issued the "abort" command, followed by "start all". When I exited > lpc, everything was back to normal. > > YMMV, though. I don't know why it happend (and yes, it "fixed itself" as > mysteriously as it began...) > > - Nick > [EMAIL PROTECTED] > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
