I'm seeing random printers on our server getting locked up with staust
"waiting for subserver to exit" messages.  The problem does not seem to be
localized to any particular printer, and some printers will be printing just
fine then suddenly experience the problem.  It happens a couple of times a
day.  Our print server supports 94 queues for remote printing; we only see
tens of jobs a day through it so it's not a busy server problem.

I've seen a number of references to this problem in the mailing list
archives but very few followup messages, none of which seems to be relevant
to my particular problem.  Anyone have any ideas?

Configuration Specifics
-----------------------

LPRng Version: LPRng-3.8.19, Copyright 1988-2002 Patrick Powell,
<[EMAIL PROTECTED]>

Printcap definition for typical printer:

  .common:sh:
        :sd=/spool/output/%P:                   \
        :lf=/spool/log/%P.log:                  \
        :lo=/spool/lock/%P.lock

  4S79-hp4200pc:tc=.common:[EMAIL PROTECTED]:cm=HP LaserJet 4200TN in
room 4S79:

The lpd.conf file is the default installed by the installation procedure.

Printers are all HP type, manly 4200s and 8150s.  Print driver used by lpd
defaults to raw (JetDirect).

There is no accounting server specified.

Thanks!

Mike



-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address

If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body.  For the impatient,
to subscribe to a list with name LIST,  send mail to [EMAIL PROTECTED]
with:                           | example:
subscribe LIST <mailaddr>       |  subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr>     |  unsubscribe lprng [EMAIL PROTECTED]

If you have major problems,  send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------

Reply via email to