Ouch.

I just noticed the following problem.

There are four things a user might want:

 1. Disable a service.
      rcctl disable service
    always does that,
    and you can compare the output of
      rcctl status service
    to "NO" to decide whether running that is actually needed.

 2. Enable the service with default arguments.
      rcctl enable service flags
    (now, after the recent change) always does that.

 3. Enable the service with custom arguments.
      rcctl enable service flags custom
    always does that,
    and you can compare the output of
      rcctl status service
    to "custom" to decide whether running that is actually needed.

 4. Enable the service *without* any arguments (even if it has
    default arguments).
    I see no way to do that with rcctl(8).
    You have to edit /etc/rc.conf.local manually and put:
      service_flags=" "

It seems that being unable to comply with request 4 is a problem.

Besides, in this thread, it seems to me that request 2 and request
4 are sometimes confused with each other.  My impression is that
for a management tool, it is useful to offer all four options to
the administrator, as well as allowing to explicitly switch from
any of them to any other of them, including explicitly switching
from request 2 to request 4 and vice versa.

Take identd(8) as an example.  It has
  daemon_flags="-e"
by default.  If i don't want that, the easiest workaround i see
is saying
  rcctl enable identd flags -t 120
that is, specifying some flags that restate defaults, just to have
*some* custom flags.  What if a daemon has no unrelated flags that
can be abused in this way?

Or do you think i'm inventing pointless complication here?

Yours,
  Ingo

Reply via email to