We use LPRng instead of CUPS because of CUPS' chattyness. We have literally
thousands of printers defined (over 7000) and the printcap defining these
printers is installed on over 100 servers. CUPS would overrun our network.
CUPS is a great design for a desktop client and one or two printers; it
really fails when you attempt to scale it up to an actual server level.
--
.~. Robert P. Nix Mayo Foundation
/V\ RO-OE-5-55 200 First Street SW
/( )\ 507-284-0844 Rochester, MN 55905
^^-^^ -----
"In theory, theory and practice are the same, but
in practice, theory and practice are different."
On 10/20/07 3:56 AM, "John Summerfield" <[EMAIL PROTECTED]>
wrote:
> Patrick Spinler wrote:
>
>>
>> Another example is managing a shared, platform heterogeneous
>> distributed printer database. Linux LPRng software from the
>> distributors works out of the box, simply by copying a common printcap
>> around. We have to compile and support LPRng for AIX ourselves, and
>> disable the native qconfig. We could copy qconfig files between AIX
>> boxes, but certainly not to any non-AIX platform like solaris, hp-ux,
>> or linux.
>
> I use cups. Printers come and go on my Linux laptop, according to where
> I go. CUPS servers can be configured to chat to each other, and my Linux
> (and OS X) laptop runs CUPS.
>
> Printing on Linux works as well as wireless on OS X.
>
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
