[Bug 783379] New: Job type reload is not applicable for unit cups.service.
https://bugzilla.novell.com/show_bug.cgi?id=783379 https://bugzilla.novell.com/show_bug.cgi?id=783379#c0 Summary: Job type reload is not applicable for unit cups.service. Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 0 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Printing AssignedTo: jsmeix@suse.com ReportedBy: suse-beta@cboltz.de QAContact: jsmeix@suse.com Found By: Beta-Customer Blocker: --- I noticed this while guttenprint was updated, but it's also reproducable with a plain "rccups reload": # rccups reload redirecting to systemctl Failed to issue method call: Job type reload is not applicable for unit cups.service. You probably need to add a "ExecReload" line to cups.service. See bug 754544 for a similar case. -- 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=783379 https://bugzilla.novell.com/show_bug.cgi?id=783379#c1 Johannes Meixner <jsmeix@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsmeix@suse.com Component|Printing |Basesystem Platform|x86-64 |All AssignedTo|jsmeix@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com QAContact|jsmeix@suse.com |qa-bugs@suse.de Summary|Job type reload is not |systemd: job type reload is |applicable for unit |not applicable for unit |cups.service. |cups.service. OS/Version|Other |SUSE Other --- Comment #1 from Johannes Meixner <jsmeix@suse.com> 2012-10-04 09:42:55 CEST --- This is not a printing issue but a systemd issue. Therefore I change the bug's component to "basesystem" (hoping this is the right one for systemd issues). I don't have sufficient knowledge about systemd. I would appreciate it if someone who knows about systemd would fix this in the cups package. -- 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=783379 https://bugzilla.novell.com/show_bug.cgi?id=783379#c Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |fcrozat@suse.com |ovo.novell.com | -- 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=783379 https://bugzilla.novell.com/show_bug.cgi?id=783379#c2 Michal Vyskocil <mvyskocil@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |mvyskocil@suse.com InfoProvider| |fcrozat@suse.com --- Comment #2 from Michal Vyskocil <mvyskocil@suse.com> 2012-10-09 09:11:51 UTC --- The following line ExecReload=/bin/kill -HUP $MAINPID have to be added to cups.service @frederic: maybe it can be a reasonable default for all units (w/o type simple)? -- 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=783379 https://bugzilla.novell.com/show_bug.cgi?id=783379#c3 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|fcrozat@suse.com | --- Comment #3 from Frederic Crozat <fcrozat@suse.com> 2012-10-09 13:03:57 UTC --- (In reply to comment #2)
This would need to be discussed with upstream, but I'm not sure it is a good idea, since you can't be sure what would be the effect on various services (you can't be sure they will all react to -HUP correctly). ATM, this line is specified in the documentation (man systemd.service, search for ExecReload). -- 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=783379 https://bugzilla.novell.com/show_bug.cgi?id=783379#c4 Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|12.3 Milestone 0 |12.3 Beta 1 --- Comment #4 from Christian Boltz <suse-beta@cboltz.de> 2013-01-20 20:33:24 CET --- This bug still exists in 12.3 beta1 :-( I see two options here: a) fix cups.service - that would be the best option, but... [1] b) fix gutenprint %post, for example by using "restart" instead of "reload" [1] according to /etc/init.d/cups, reload isn't that easy: reload) if ps -C cupsd -o user | grep -q '^root$' then echo -n "Reload service cupsd" killproc -HUP $CUPSD_BIN rc_status -v else echo -n '"reload" not possible (cupsd does not run as user root) use "restart" instead' rc_status -s fi I don't know if this (running cups as non-root) is relevant in real-world setups - Johannes? -- 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=783379 https://bugzilla.novell.com/show_bug.cgi?id=783379#c5 --- Comment #5 from Johannes Meixner <jsmeix@suse.com> 2013-01-22 09:40:06 CET --- No other package (except cups) should stop and start (i.e. restart) a currently running cupsd at arbitrary time (e.g. during package installation) because this disrupts all currently active print jobs. This is in particular bad on print server machines (admins do not expect such behaviour because of our obscure packaging dependency). And also on home-user systems it can cause major annoyance when unexperienced users do not know how to easily recover a printer that has become "mad" because it was disrupted during active printing (i.e. how to do a complete reset of the printer device while there is a print job in the queue). Only printer admin tools may stop or start the cupsd if really needed but even then I recommend an explicit admin confirmation dialog, compare "Strict Compliance With CUPS" at http://en.opensuse.org/Archive:YaST_Printer_redesign ----------------------------------------------------------------------------- The YaST printer module up to openSUSE 11.0 ... does not work in full compliance with the CUPS printing system. ... It re-starts the cupsd much too often (each time when it finishes) which disrupts all actively printing jobs (really bad on a print server under higher load). ----------------------------------------------------------------------------- Regarding sending CUPS daemon SIGHUP in gutenprint.spec, see https://bugzilla.novell.com/show_bug.cgi?id=637455#c3 -- 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=783379 https://bugzilla.novell.com/show_bug.cgi?id=783379#c Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|fcrozat@suse.com |systemd-maintainers@suse.de -- 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=783379 https://bugzilla.novell.com/show_bug.cgi?id=783379#c6 Johannes Meixner <jsmeix@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE --- Comment #6 from Johannes Meixner <jsmeix@suse.com> 2014-02-14 15:43:13 CET --- I think this issue here is meanwhile obsolete since https://bugzilla.novell.com/show_bug.cgi?id=857372#c61 and subsequent comments. *** This bug has been marked as a duplicate of bug 857372 *** http://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