On 21 December 2016 at 08:13, Martin Pitt <[email protected]> wrote: > > Till Kamppeter [2016-12-19 16:48 -0000]: > > Then edit the file /lib/systemd/system/cups.path adding a line > > "PartOf=cups.service" to the [Unit] section, so that the file looks like > > this: > > > > ---------- > > [Unit] > > Description=CUPS Scheduler > > PartOf=cups.service > > I suppose that cups.path is only for booting, i. e. you want to start > cups.service on boot, not again on demand on a running system. Does it ever > happen that cups.service terminates by itself due to inactivity? If not, this > provides a good enough workaround for not stopping cups.path properly in the > maintainer scripts. If yes, this appproach doesn't work. > > Note that you probably want to do the same for cups.socket, with the same > reasoning as above. >
I'm not sure, but I thought we want to keep cups.socket around, after cups.service self-shutdowns during normal system operation, because we want to keep cups.service socket activatable. IMHO cups.path should be removed, and instead a generator used to add cups.service to multi-user.target.wants on boot if the state file indicates we want cups.service to be always running. -- Regards, Dimitri. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642966 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
