On Mon 27 Jul 2015 at 14:17:52 +0200, Tuxo Holic wrote: > > On Sun, 26 Jul 2015 20:28:21 +0100, Brian wrote: > > > Your problem (please correct me if I have not understood what you said) > > is that applications, Iceweasel, Evince etc, still see HP_LaserJet_1020 > > after the server is closed down. > > No, I meant: the server usually stays on until I go to bed, but the > printer is switched off right away as soon as I no longer use it. > Clients still see that printer, even after I switched it off. > And: they also see that printer, if only the server started, with the > printer still beeing switched off.
Clients see print *queues*, not printers. Print queues are advertised by the server. The on/off status of the printer is immaterial. If you do not want the clients to see the queues do systemctl stop avahi-daemon.service at the same time you switch off the printer. > >> >> BrowseAllow 192.168.1.1 > >> BrowseAllow Server1 > >> BrowsePoll Server1:631 > > > > Into unknown territory! What's wrong with the defaults? Your server is > > advertising; the default 'BrowseRemoteProtocols dnssd cups' on the > > clientworks well, What need is there for these? > > One problem here: The advertising with the default values doesn't work > since every line responsible for "Browsing" is disabled with a > comment. For advertising to work on the client, I need at least one > valid line with either the Printserver IP or the Printserver Hostname > or the Printserver Subnet. Your server broadcasts Bonjour packets. Your client machines pick them up and, with the help of cups-browsed, create local raw queues. There is no need for the server to use CUPS broadcasts or have cups-browsed on it. > > What versions of cups are running on the clients? > > Debian/Jessie on client & sever > 1.7.5 > This means: it is newer than 1.6 thus needs the cups-browsed package > to advertise network printers, right? Only needed on the client to browse Bonjour broadcasts, not for advertising. Please see cups-browsed(8) and the README.Debian for cups. > A question here: Do I need to install it on the server as well? Only if you want it to broadcast queues using the CUPS protocol. Do you? Why? > Because like I explained I only changed the client configuration, but > I changed nothing on the server, which means: I installed both cups & > cups-browsed there as well, but left the configuration unchanged as > far as configuring the printer using the cups webinterface goes: > > Find printer > select recommended driver > add printer > select share this > > printer > save changes > cups restarted. > I'm not even sure I absolutely need cups on the client ... it might be enough > to have cups-browsed installed there, in order to find my network printer. You should try it. :) > Can you elaborate on the role cups and cups-browsed share these days? Do both > services have to run on client AND server? Please see above. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150727162058.gc...@copernicus.demon.co.uk
