[cups] Is client.conf really deprecated on all platforms?
Michael Sweet
msweet at apple.com
Mon Nov 2 07:50:44 PST 2015
Andreas,
> On Nov 1, 2015, at 5:28 AM, Andreas Radke <a.radke at arcor.de> wrote:
>
> Am Fri, 30 Oct 2015 13:01:15 -0400
> schrieb Michael Sweet <msweet at apple.com>:
>
>>
>> The local cupsd can coordinate with the OS to keep the system (and
>> network stack) up long enough to send the job remotely. The local
>> cupsd can also handle conversions of application supplied print data
>> into a printable form. And the application won't block for as long -
>> local domain sockets are several orders of magnitude faster than
>> network sockets.
>
> From what I know all major Linux distribution ship separate cups client
> packages using a client.conf file and do not rely on a running local
> cupsd server. Should this be changed?
That's a choice for the Linux distros, but it has never been a configuration we've supported with our build system or sample packaging files, nor is it a recommended configuration because of all of the problems I've stated previously.
_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair
More information about the cups
mailing list