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.