On Fri, Nov 06, 2026 at 02:59:20PM +0100, Paolo Aglialoro wrote:
> Hello,
>
> just a question. What is the design logic behind this:
>
> rcctl ls on ----> normal user can execute this command
> rcctl ls started ----> only root can execute this command
>
> shouldn't also the "started" services be visible to normal user? (I'd prefer
> this one)
> or shouldn't also "on" be denied to normal user?
> is this coping with some remote risk or just happens to be like this?
The design logic is:
rcctl ls on:
check the service is activated in the config
i.e. mostly read rc.conf{.local}, no superuser rights needed
rcctl ls started:
will run "/etc/rc.d/foo check" => some rc.d scripts needs root permission to do
that.
--
Antoine
