Moving a Print Server from Solaris to Linux


We have a Solaris print server that serve more than 2000 Unix
workstation (Sun,SGI,Linux...) and we use LPD System to print

Right now we want to move from Solaris server to linux and we want to
use CUP system and we don't want our user to change there way to print
(lpr -P Prs12 /etc/fstab ) because they have many scripts that use the
command lpr

My question is there any how-to or a book that can help me so I can be
able to Setup CUPs to allow anyone to send a job to it and allow it to
receive LPD jobs

Thank you
Who is Participating?
ee_ai_constructConnect With a Mentor Commented:
Please read entire thread.  Asker solved or content important.
Closed, 250 points refunded.
ee_ai_construct (replacement part #xm34)
Community Support Admin
As of CUPS 1.1 the LPD protocol is supported allowing legacy print services to send jobs to a CUPS print serer. So this should be just a matter of enabling client access to CUPS and pointing the clients at the CUPS server. Generally, CUPS will default to accept print jobs from anywhere/anyone, but a specific OS implementationmight restrict jobs to be from only the local machine.
MrAhmadAuthor Commented:
I started the servie cup-lpd in the server but when I try to print from the client using lpd  I got :

Error: loop in printcap- optrac710@lnx3c022 -> optrac710@localhost

Note ( the host : lnx3c022 is the  client host name not the server)

I don't now what is the problem
A proven path to a career in data science

At Springboard, we know how to get you a job in data science. With Springboard’s Data Science Career Track, you’ll master data science  with a curriculum built by industry experts. You’ll work on real projects, and get 1-on-1 mentorship from a data scientist.

What printers have you defined and where are they?

What printer was the client rying to print to?
MrAhmadAuthor Commented:
Ok now I am able to print without any problem using Linux (the problem was that I have to restart the LPD daemon to be able to use the new printers :) )

And I found a very good how-to at
Any time you add or remove a printer it is necessary to restart the scheduler since it only reads its config files at startup. The Gui interface to CUPS and the Gui printer management interfaces on Linux will either do this automatically, or give you and option to do so. If you do direct manipulation of the config you just need to restart CUPS.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.