[Bug 863570] New: systemd cups.socket listening only on unix domain socket plus using desktop magic for remote queue browsing
https://bugzilla.novell.com/show_bug.cgi?id=863570 https://bugzilla.novell.com/show_bug.cgi?id=863570#c0 Summary: systemd cups.socket listening only on unix domain socket plus using desktop magic for remote queue browsing Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: All OS/Version: openSUSE 13.2 Status: ASSIGNED Severity: Enhancement Priority: P5 - None Component: Printing AssignedTo: jsmeix@suse.com ReportedBy: jsmeix@suse.com QAContact: jsmeix@suse.com CC: lnussel@suse.com, speilicke@suse.com Found By: Development Blocker: No See https://bugzilla.novell.com/show_bug.cgi?id=857372#c91 and https://bugzilla.novell.com/show_bug.cgi?id=857372#c102 and https://bugzilla.novell.com/show_bug.cgi?id=857372#c108 Summary: Having /usr/lib/systemd/system/cups.socket ------------------------------------------------------------------ [Unit] Description=CUPS Printing Service Sockets [Socket] ListenStream=/var/run/cups/cups.sock [Install] WantedBy=sockets.target ------------------------------------------------------------------ it would only care for the unix domain socket. This would result in cups starting up as soon as you want to print, then cupsd's config determines whether it listens on IP sockets as well. This cups.socket plus an automated "lpstat -h /run/cups/cups.sock -r" during user log in could implement cupsd socket activation with static cups.socket that is secure and works also in a real network. But an automated "lpstat -h /run/cups/cups.sock -r" during log in plus cupsd socket activation results basically the same as an automated cupsd start at system boot. But that is up to the desktop then. If you have a desktop that doesn't fiddle with the printing cups won't be started. In that case you have to wait for printers to appear indeed. Or if you know your workstation is in a cups enabled network you just enable cups.service. Same for servers, just enable cups.service. Still cups.socket should only have the unix domain socket. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=863570 https://bugzilla.novell.com/show_bug.cgi?id=863570#c Johannes Meixner <jsmeix@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=863570 https://bugzilla.novell.com/show_bug.cgi?id=863570#c1 Johannes Meixner <jsmeix@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.novell.com | |/show_bug.cgi?id=861084 --- Comment #1 from Johannes Meixner <jsmeix@suse.com> 2014-02-12 17:58:27 CET --- This method here could be an alternative to bnc#861084 "systemd generator to create cups.socket that matches cupsd.conf". The advantage here is the static cups.socket file. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=863570 https://bugzilla.novell.com/show_bug.cgi?id=863570#c Johannes Meixner <jsmeix@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.novell.com | |/show_bug.cgi?id=857372 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com