One of the LPRng list readers sent me a description of the a 'mysterious
print job migration' problem, where he would send a job to one queue and
it would appear on another.
I was puzzled, until I remember a similar problem.
This was the 'disappearing print job'. The job would be sent and
would then disappear from the queue without being printed.
The problem was that the person had created TWO (actually, ALL)
of the print queues with the same spool directory:
lp1:sd=/var/spool/lp
...
lp2:sd=/var/spool/lp
...
lp3:sd=/var/spool/lp
...
lp4:sd=/var/spool/lp
This was the result of using cut and paste from an existing print queue.
I strongly recommend using:
lp1:sd=/var/spool/%P
...
lp2:sd=/var/spool/%P
...
lp3:sd=/var/spool/%P
...
lp4:sd=/var/spool/%P
Which will create unique spool queues..
Patrick 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.
-----------------------------------------------------------------------------
