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

bugtracker-admin at leaf.dragonflybsd.org bugtracker-admin at leaf.dragonflybsd.org
Sat Jan 7 03:50:30 PST 2023

Issue #3328 has been updated by mneumann.

Hey everybody, 

I think the issue I was having with this was that dhcpd would not start up at boot time when just giving "dhcpd=YES", or it would not start up when issuing "service dhcpd restart". It might start up with "/etc/rc.d/dhcpd start". IIRC, one of the three things did not work, that's how I noticed the problem. I cannot test this at the moment, but if someone else wants to research this, that'd be great. I might also be completely wrong and my brain cells are leaky. (I should have mentioned this in the issue in the first place).

I think one problem could be the /etc/rc/defaults/rc.conf that contains a `dhcpd_enable=NO` and this might get confused with a `dhcpd=YES` in some way. IIRC, I got similar issues with other services, where calling the script directly would work, while running it via `service abc start` would not.

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