Hi.
uname -rsv
OpenBSD 5.0 GENERIC#39
I'm gearing up to use popa3d and testing it on a machine.
I tried the following in rc.conf.local (where V is version number and
exeunt) ...
popa3d_flags="-D"
popa3d_flags="-V"
popa3d_flags="-D -V"
... and it does not start.
Even though I see this in RC.D(8) ...
Services comprising OpenBSD base are
started by rc(8).
... and this in RC.CONF(8) ...
This file contains a series of Bourne-shell syntax assignments that are
used to configure the system daemons.
... and these in RC(8) ..
rc is the command script that is invoked by init(8) when the system
starts up. It performs system housekeeping chores and starts up system
daemons.
Normal-
ly, rc.local contains commands and daemons that are not part of the stock
installation.
A quick (quick) grep of rc (and rc.conf) shows that while other
services in base are there popa3d is absent in both.
Is this an oversight for popa3d (and perhaps others) that aren't
included in rc but are in base?
Is this intended by the use of "Normally" in rc(8) and do those other
man pages warrant re-wording?
So I added popa3d to rc.local and that works although I'm not sure if
the intended method is to merely pop the command in there ...
popa3d -D
... bypassing rc.conf.local flags or some other method.
Doing thiss I get no feedback on whether or not popa3d has started
other than looking at ps -x ...
It doesn't seem to matter whether or not I have a popa3d file in rc.d ...
This doesn't seem to be the intent of rc.d(8).
If I mv some of the other files related to rc services in rc.d
(notably ntpd and smtpd) I get an error message at boot when I try to
start those services.
Has popa3d or rc.local slipped through the cracks?
I added popa3d to pkg_scripts= in rc.conf and that appears to function
as intended (rc.conf.local flags obeyed and requires file in rc.d).
Best wishes.
