We help IT Professionals succeed at work.

Printing in Unix, is it a good choice

cl071997 asked
Last Modified: 2013-12-06
We have 200 printers, most of them is HP, connected via jetdirect. We are running HP-UX and there is a lot of traffic on the printers.
We need to change it and the choice is BSD lpd. I have heard that its pretty buggy and not a good choice as printerserver. Is linux an alternative (among the BSD alternative)?

Claes Lindvall
Watch Question

Top Expert 2005

By "lpd" do you mean sending data to the JetDirect interface via its built in lpr interface? Or do you mean changing from the lp print system to the lpd print system on HP-UX?


I mean changing from lp print system to lpd.


What do you hope to get out of this?  Network traffic will not be reduced by setting up an intermediate print server - in fact it will double:  
HP---(Print job)-->Printer Server---(Print Job)-->Printer
HP<--( Status )---Printer Server<--( Status )---Printer

If the HP server is acting as a print server to other systems to simplify printer management, (rather than the other systems communicating direct with the JetDirect "print servers"), your plan will reduce the load on the HP-UX box
(space in /var/spool & traffic on the network card).

I doubt whether Linux (or any other Unix) will communicate with an HP printer "better" than HP-UX, but it is cheap and easy to set up and maintain as a print server.  HP-UX is quite happy using lpd - I've had no problems at the HP-UX end, but getting the true status of the printer from the print server can be confusing.

You may also want to try using Windows NT as an lpd print server - cheap, quite
reliable, not too hard to set up and easy to maintain and interface with.

Top Expert 2005

Why would you want to change from lp to lpd? The lpr system might be slightly more efficient talking to the printer, but I doubt that it would make a measureable difference in traffic.

If you've got 200 printers it almost sounds like there might be a more fundamental network design problem.


I will be more specific...
The situation is as follows:

We are running a pretty heavy application on a hp-box no.1 and a lot of printing is coming out from the appl.
The HP-box no.1 is heavily loaded (primary because of the application) and we have to move the queing and filter-stuff (it takes some cpu to filter every printjob, we are using jetadmin and that seems to take even more cpu, and we are talking a lot of printing).

So on the HP-box no.1 we just use remote-printing - just sending the file away to another HP-box no.2.
Now there is another application on that machine and from the beginning only a few people used it, but now...

So we need to move the printing from HP-box no.2 to a third machine (HP-box no.1 will now send their printjob
to XX-box no.3).

It´s rather costly with a new HP machine and we are looking on some intel-based OS - Free-BSD, Solaris, Linux.
I´ve heard that the lpd is not so stable as the lp printing system.

Yes, jlevie, we have 200 printers, but they are spread across sweden and the load on the network is not a problem.

Yes, tfewster, we have thought about an NT (or novell) solution, but some says that NT is not to reliable as a printerserver, and we can´t reboot the system and lose some printerjobs.

The printingstuff is a very important part in the application and availability is very important (as allways).

Thanks for your help
Top Expert 2005
This one is on us!
(Get your first solution completely free - no credit card required)


OK. Thanks for your advise.
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.