On Tue 28 Jul 2015 at 10:35:33 +0200, Tuxo Holic wrote: > Okay Brian - here's the update of further testing: > I need one BrowsePoll line enabled so the cups-browsed clients know > what hostname or IP they should poll,which leaves me with the > following *not default* but very simplistic cups-browsed.conf > > grep -v ^# /etc/cups/cups-browsed.conf > BrowseRemoteProtocols dnssd cups > BrowsePoll 192.168.1.1:631 #could use Server1 as hostname with the same effect > > LANG=C lpstat -t > scheduler is running > no system default destination > device for HP-LaserJet-1020: > ipp://192.168.1.1:631/printers/HP_LaserJet_1020 > HP-LaserJet-1020 accepting requests since Tue 28 Jul 2015 10:04:34 AM CEST > printer HP-LaserJet-1020 is idle. enabled since Tue 28 Jul 2015 10:04:34 AM > CEST
> Let me be clear, that without a BrowsePoll line I end up with no > search result in lpstat . I do not understand that. BrowsePoll is in cups-browsed to provide backwards compatibility with server versions < 1.6.x. Servers > 1.6.x do not respond to CUPS packets. BrowseRemoteProtocols dnssd should be the only line necessary for you in cups-browsed.conf. > I successfully removed the cups-browsed package from the server which > leaves cups alone to share printers on the server side. > > I can remove the cups package on the client, but doing so I end up > with cups-browsed being unusable. Reinstalling cups right away and it > will work again. Conclusion: seems to me cups should be a dependency > for cups-browsed, in Debian/Jessie. Either it is not or I messed up my > apt environment. cups-browsed is not unusable; it does not require cups-daemon in order to work, which is what is meant by a dependency. Iceweasel will display print queues without cups on the system by having avahi-daemon inform cups-browsed of the ones it knows about. Granted, libcups2 is required. > >> 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> 'systemctl stop avahi-daemon.socket' may also be needed. > I get that, but it still is cause for confusion to some people, > because there is no way to distinguish a queue of a running printer to > a queue of a *not* running printer. You can successfully hit print and > there is no feedback whatsoever in the application, that next you > should get up and switch on your printer. It only leads to confusion if you neglect to do systemctl stop cups.service cups.socket cups.path before or after switching the printer off. :) > Which brings me back to my previous question: Seems to me "server > cups" knows that printer is not running yet, how can I make "server > cups" tell this to "client cups" , so the users gets the feedback in > the printing app? My idea would be some sort of notification like > "please switch on printer "HP_LaserJet_1020" . There is a wiki page for Tea4CUPS. It might give you some ideas. -- 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/20150728145346.ga4...@copernicus.demon.co.uk
