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.
Till Kamppeter [2016-12-19 16:48 -0000]: system/ cups.path adding a line cups.service" to the [Unit] section, so that the file looks like
> Then edit the file /lib/systemd/
> "PartOf=
> 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.