Sure enough.  Thank you!

Kevin


[EMAIL PROTECTED] wrote:
> 
> > From [EMAIL PROTECTED] Thu Jul 20 12:02:09 2000
> > Date: Thu, 20 Jul 2000 11:07:22 -0700
> > From: Kevin Nomura <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED]
> > Subject: LPRng: duplicate jobs (on different printers)
> >
> > Using LPRng-3.6.12-1 on Linux redhat 6.1:
> >
> > If I submit a job to queue B while a job is active on
> > queue A, there is a chance that the job comes out on
> > both printers.  I suspect it's a misconfiguration
> > problem on my part but I have no idea where to look.
> > Has anyone else seen this or can someone suggest
> > why it might happen?
> >
> > Kevin
> 
> You have the same spool directory for both queues.
> 
> Patrick ("Been there, done that!") Powell
> 
> -----------------------------------------------------------------------------
> 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.
> -----------------------------------------------------------------------------

-----------------------------------------------------------------------------
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