[DragonFlyBSD - Bug #3328] (Closed) rcenable will not add `_enable` prefix

bugtracker-admin at leaf.dragonflybsd.org bugtracker-admin at leaf.dragonflybsd.org
Sat Jan 7 03:20:27 PST 2023

Issue #3328 has been updated by daftaupe.

Status changed from Feedback to Closed

Reporting an answer from @liweitianux on IRC

<pre><code class="shell">
02:29 <@aly> daftaupe: hi. i saw your reply to the bug regarding rcenable. the rc framework was initially developed by netbsd, and then imported to freebsd and then inherited by us.
02:30 <@aly> the netbsd version uses 'foo=YES' to enable one service; don't why freebsd changed that to 'foo_enable=YES'. and for us, both versions are supported.
02:32 <@aly> we might have mixed 'rcvar=`set_rcvar`' and 'rcvar=xxx' in base. but all ports use 'rcvar=xxx_enable', as required by freebsd's policy.

So both are expected to work. Closing as this is not a bug.

Bug #3328: rcenable will not add `_enable` prefix

* Author: mneumann
* Status: Closed
* Priority: Normal
* Target version: 6.4
* Start date: 2022-09-13
When I run

rcenable dhcpcd

I get the following line added to rc.conf:


While I'd expect it to be:


You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account

More information about the Bugs mailing list