http://bugzilla.novell.com/show_bug.cgi?id=433047
User jsmeix@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=433047#c10
Johannes Meixner changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Printer setup: Add the |yast2-printer "Print via
|possibility to config |Network": Ambiguous wording
|BrowsePoll |"receive" and request for
| |BrowsePoll support
Severity|Enhancement |Minor
--- Comment #10 from Johannes Meixner 2009-04-30 04:01:01 MDT ---
A "ServerName MYServer" entry in client.conf
forces all CUPS client programs (e.g. lpstat, lp, ...)
and all applications which use the CUPS library correctly
to contact directly the cupsd on MYServer.
Therefore a local running cupsd on a client host
is never contacted by default - except you do e.g.
lpstat -h localhost -p
or
echo Hello | lp -h localhost -d queue_name
In particular a print queue on on a client host is
therefore by default ignored.
When you want to use the queues on the server
and a local print queue on on a client host,
you must let the server send browsing information to the client hosts
(run YaST on the server and use "Share Printers" to set it up)
and on the client hosts you must accept the browsing information
from the server (run YaST on each client host and
use "Print via Network" -> "Receive Printer Information
from Remote CUPS Servers" to set it up).
This results a setup according to the
"Intrinsic design of CUPS for printing in the network"
http://en.opensuse.org/SDB:CUPS_in_a_Nutshell
By the way 1:
In any case I will change the wording in strings like
"Recieive Printer Information from Remote CUPS Server"
because the "receive" does not make clear if this happens
actively (i.e. polling via BrowsePoll) or only
passively (via BrowseAllow).
In the current YaST it happens passively (via BrowseAllow)
so that I will change the wording to something like
"Accept Printer Information from Remote CUPS Server"
Therefore it is now a "minor" bug.
By the way 2:
I know a use-case for BrowsePoll:
When in a bigger company there are several CUPS servers
for various departments each server may allow access for
all client hosts in the whole company but it would usually
send browsing information only to the client hosts of the
particular department to which a particular server belongs.
When a user in department A likes to see additionally
the queues on the server for department B he would use
BrowsePoll to poll the queues from the server for
department B.
Adding BrowsePoll support requires a re-design of the
whole "Print via Network" dialog.
Therefore I must file a FATE feature request
so that it can be evaluated if it is worth the effort
("business case" and so on).
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.