Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

LPR and "No Daemon Present"

445 views
Skip to first unread message

Thomas/Shurflo

unread,
Mar 8, 2000, 3:00:00 AM3/8/00
to
Anyone know why this message appears in the output of "lpc status"?

I've heard that it appears when there are no print jobs present, but I
have a printer setup (Samba uses it) with two print jobs waiting to
print and the same message. Here is the status

HP4DP:
queuing is enabled
printing is enabled
2 entries in spool area
no daemon present

Anyone know how to optimize printing on a Linux box? I want printing to
occur immediately with high priority. Currently the print queue just
seems to wait and wait.

I can send restart the print queues with "lpc restart printer" but I
don't understand why I have to restart them.

Anyone?


lucvanb...@my-deja.com

unread,
Mar 14, 2000, 3:00:00 AM3/14/00
to
In article <38C6A94D...@shurflo.com>,

Thomas/Shurflo <tho...@shurflo.com> wrote:
> Anyone know why this message appears in the output of "lpc status"?
> ....

> HP4DP:
> queuing is enabled
> printing is enabled
> 2 entries in spool area
> no daemon present
>
> I can send restart the print queues with "lpc restart printer" but I
> don't understand why I have to restart them.
>
I am having the same problem, and I would like to see an answer.
I have noticed that the daemon dies after he was unable to send
the printjob to the printer (e.g. power off, no paper, ...)
but the daemon should resume after the fault is restored....

Looking forward to a solution

Luc Van Bockstal


Sent via Deja.com http://www.deja.com/
Before you buy.

Andre Deparade

unread,
Mar 16, 2000, 3:00:00 AM3/16/00
to tho...@shurflo.com
Thomas/Shurflo wrote:

> I've heard that it appears when there are no print jobs present, but I
> have a printer setup (Samba uses it) with two print jobs waiting to
> print and the same message. Here is the status
>

> HP4DP:
> queuing is enabled
> printing is enabled
> 2 entries in spool area
> no daemon present

If you are using a recent version of "lprold" from Suse: due to a "bug"
in the lpr-package. AFAIK their package-maintainer fixed a security bug
and introduced this one. The message "no daemon present" is reported, if
you enter "lpc status" right after starting the lpd-daemon.

dpi

0 new messages