Hello,
The setup is:
- 1 HP LJ printer with JetDirect
- 2 lprng queues both printing to port 9100 of JD
My question is: does lprng SW some kind of destination device locking?
(so sending job to both queues at the *same* moment will not result at
two lpd daemons to try to send job to a port
On Thu, 6 Nov 2003, Dan Bar wrote:
DB
DB Hello,
DB
DB The setup is:
DB
DB - 1 HP LJ printer with JetDirect
DB - 2 lprng queues both printing to port 9100 of JD
DB
DB My question is: does lprng SW some kind of destination device locking?
DB (so sending job to both queues at the *same* moment will
The way this is done is to implement bounce queues. Neither of the two
queues actually talks to the printer. Instead the third one does. The
first two printers merely pass the jobs on to this third one.
If you provided why you need this functionality, it might be easier to
assist you more
By the way, unfortunately, the Fedora Core project (the replacement
for the free RedHat Linux distribution) seems to be using CUPS only
only according to the release notes. Replacing it with LPRng might be
problematic because many other packages probably depend on it.
-akop
On Wed, Nov 05,
I'm just looking at upgrading from a seriously ancient LPRng 3.6.13 to
3.8.22.
I've set up a test machine with the new version running and have noticed
a problem that I wonder if others are seeing.
If a user doesn't have permission to print on a particular printer (ie:
lpd.perms file contains
