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

Re: documenting on how not starting a daemon upon installation

On Mar 11, Marvin Renich <mrvn@renich.org> wrote:

>   - it has not been mentioned whether systemd provides any facility to
>     block starting _all_ services for a period of time (esp when working
>     in a chroot), including services that have not been installed at the
>     time the hypothetical "block all services" command is invoked.
systemd cannot start services in a chroot anyway because there is no 
systemd daemon there, so it does not matter for this use case.

>   - policy-rc.d can block individual systemd services and init scripts.
>   - policy-rc.d can block all services and init scripts.
>   - policy-rc.d is not well documented.
>   - policy-rc.d requires manually writing a shell script (a trivial
>     one-liner for the "block all" case).
But only if the daemons are started using invoke-rc.d.


Attachment: signature.asc
Description: PGP signature

Reply to: