[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: "Main Switch" to turn off CUPS totally when we use systemd as PID 1




Hello,

On Aug 15 15:39 Tim Waugh wrote (excerpt):
On Thu, 2014-08-14 at 19:48 +0200, Till Kamppeter wrote:
Especially Johannes Meixner told me that the current systemd
configuration is missing a "Master Switch"  to not only stop cupsd but
also to tell that it should not be started on-demand. Currently you have
only the possibility to stop the daemon butt systemd is still listening
on the sockets and therefore CUPS gets started as soon as someone
accesses port 631 or connects a USB printer.

The 'master switch' is this:

systemctl disable cups.{socket,path,service}
systemctl stop cups.{socket,path,service}

No.
Those are the individual switches.

See
https://bugzilla.novell.com/show_bug.cgi?id=864894
what I mean with "master switch".

Summary:

Assume for "the whole CUPS thing" there are those unit files:
  cupsd.service
  cupsd.socket
  cupsd.path
  cups-lpd.socket
  cups-browsed.service
  cups-browsed.socket

For example to completely switch off "the whole CUPS thing"
one may have to do (depending on what is actually active):
# systemctl stop cupsd.service
# systemctl stop cupsd.socket
# systemctl stop cupsd.path
# systemctl stop cups-lpd.socket
# systemctl stop cups-browsed.service
# systemctl stop cups-browsed.socket

I would like to have a "master switch" unit file e.g. named
  cups.service
so that only one single command
# systemctl stop cups.service
is needed for "the whole CUPS thing" (also for start/enable/disable).


Kind Regards
Johannes Meixner
--
SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany
HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer


Reply to: