-
Notifications
You must be signed in to change notification settings - Fork 23.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
service module does not work on FreeBSD, if startup script name differs from the "rcvar" #3382
Comments
Thanks, if you can take a crack at this, it would be much appreciated! |
As a note to future myself or anyone else investigating this, here's a list of services I've encountered so far that suffer from this issue:
Also possibly sendmail. |
Sendmail's situation is more complex. It seems that a single script in rc.d can launch several daemon processes, each which have their own rcvars. So
|
Some services have a knob (i.e. rc.conf setting) whose name differs from that of the script. For example, lockd process is controlled with a script called lockd, but the rc.conf value is rpc_lockd_enable. Fixes issue #3382.
merged the above so should be able to close this |
Remove need for translate/maketrans due to py3 differences
Setting up a service on FreeBSD requires writing an rcvar line, i.e. "XXX_enabled = yes" to /etc/rc.conf and starting the daemon via startup script via the service tool.
At least for avahi-daemon, the names of the startup script and the rcvar differ. The startup script is called avahi-daemon, but the rcvar is avahi_daemon_enable. This breaks the FreeBSD service module for avahi-daemon.
It is possible to dig up the rcvar with the service command:
The change looks easy enough, so I can provide a pull request once I've had time to work on it. However, I don't have time to work on it for at least for the few next days. If some one else wants to pick this up, feel free.
The text was updated successfully, but these errors were encountered: