public inbox for printing-architecture@lists.linux.dev
 help / color / mirror / Atom feed
From: "Beyer, Christoph" <christoph.beyer@desy.de>
To: Printing-architecture@lists.linux-foundation.org
Subject: [Printing-architecture] driverless clients after cups upgrade and general qyestion about larger environment concepts
Date: Wed, 8 Mar 2023 09:03:00 +0100 (CET)	[thread overview]
Message-ID: <1694880310.2965478.1678262580752.JavaMail.zimbra@desy.de> (raw)


Hi,

I am new on this list and would like to bother you with a (maybe stupid question) right away :) 

I do run a 'large' environment with roughly 1.000 queues pointing to 500 printers, the current setup involves a lpd server as a backend talking to the printers and different cups servers for different departments offering the relevant share of the queues to the LINUX clients. 

I use the factory provided PPD files for the printers and lpadmin to install the printers on the cups server (with an lpd backend pointing to the lpd server) then poll-server <cups-server-of-this-department> directive in cups-browsed.conf on the LINUX client.

After a recent upgrade to CUPS 2.4.1 on the cups servers (coming from ubuntu 18.04- whatever cups version that was)  support for color printing stopped and on the clients desktops I recognize that the printers are visible but tagged as 'driverless' which is probably part of my problem (?)

Maybe the whole concept is also a bit ignorant towards the ideas of cups but for quite a while I did not really see the concept of a client-server model for larger entreprise installations that can not rely on browsing etc.  ? 

Any insight would be much appreciated ! 

Best
christoph

             reply	other threads:[~2023-03-08  8:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08  8:03 Beyer, Christoph [this message]
2023-03-08 11:22 ` [Printing-architecture] driverless clients after cups upgrade and general qyestion about larger environment concepts Zdenek Dohnal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1694880310.2965478.1678262580752.JavaMail.zimbra@desy.de \
    --to=christoph.beyer@desy.de \
    --cc=Printing-architecture@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox