From: Till Kamppeter <till.kamppeter@gmail.com>
To: Open Printing <printing-architecture@lists.linux-foundation.org>,
Michael Sweet <msweet@apple.com>
Subject: [Printing-architecture] cups-browsed - What to do if client.conf redirects to remote CUPS
Date: Mon, 05 Aug 2013 23:42:19 +0200 [thread overview]
Message-ID: <52001C3B.8090602@gmail.com> (raw)
Hi,
cups-browsed works well browsing printer broadcasts from remote servers
and auto-adding local raw queues pointing to these printers as long as
CUPS clients are not redirected to remote servers via /etc/cups/client.conf.
If there is such a re-direction, cups-browsed does not make much sense,
as it cannot manipulate CUPS queues on a remote server. It can even
misbehave, as
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1207203
shows.
What I would like to do is to make cups-browsed always connecting to the
local CUPS daemon, ignoring any client.conf setting. Is this easily
possible?
Or should I better simply on the first failed attempt to add or remove a
print queue make cups-browsed shutting down and enter a stand-by loop
until the cupsServer() output changes?
Till
next reply other threads:[~2013-08-05 21:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 21:42 Till Kamppeter [this message]
2013-08-05 23:35 ` [Printing-architecture] cups-browsed - What to do if client.conf redirects to remote CUPS Michael Sweet
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=52001C3B.8090602@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=msweet@apple.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.