I tried that too. Still no luck. However, here is the lpc status all now...
lp35_05:
queuing is enabled
printing is enabled
no entries
no daemon present
lp35A:
queuing is enabled
printing is enabled
5 entries in spool area
lp35A is ready and printing
lp35:
queuing is enabled
printing is enabled
8 entries in spool area
waiting for lp35 to become ready (offline ?)
Which shows no change from when I implemented Nick's suggestion.
Thanks anyway.
Ron
./.
> 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
>
>
> --
> Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] <
/dev/null
>
>
