Is there a reason that initctl couldn't respect /usr/sbin/policy-rc.d?
Especially since any real-world policy-rc.d file just exits 101 (disallowed) 99% of the time, it doesn't seem too problematic if sysadmins have to rewrite theirs to deal with a few more potential arguments from initctl.
Is there a reason that initctl couldn't respect /usr/sbin/ policy- rc.d?
Especially since any real-world policy-rc.d file just exits 101 (disallowed) 99% of the time, it doesn't seem too problematic if sysadmins have to rewrite theirs to deal with a few more potential arguments from initctl.