FYI:
CUPS 2.0.0 with upstream support for systemd socket activation (cf. bug#857372) does not yet "just work", see for example https://www.cups.org/str.php?L4497
Furthermore there is the open issue how the systemd unit files should be named, see the "systemd unit files and service names" mail thread on the CUPS developer list <email address hidden> http://cups.org/pipermail/cups-devel/2014-October/thread.html in particular http://cups.org/pipermail/cups-devel/2014-October/015368.html http://cups.org/pipermail/cups-devel/2014-October/015369.html http://cups.org/pipermail/cups-devel/2014-October/015372.html
FYI:
CUPS 2.0.0 with upstream support for systemd socket activation /www.cups. org/str. php?L4497
(cf. bug#857372) does not yet "just work", see for example
https:/
Furthermore there is the open issue how the systemd unit files cups.org/ pipermail/ cups-devel/ 2014-October/ thread. html cups.org/ pipermail/ cups-devel/ 2014-October/ 015368. html cups.org/ pipermail/ cups-devel/ 2014-October/ 015369. html cups.org/ pipermail/ cups-devel/ 2014-October/ 015372. html
should be named, see the "systemd unit files and service names"
mail thread on the CUPS developer list <email address hidden>
http://
in particular
http://
http://
http://