Re: Bug#700245: freebsd-utils: some initscripts start twice
On 10/02/13 14:27, Steven Chamberlain wrote:
> I noticed some initscripts are running twice at startup. The
> Default-Start flag should usually choose either runlevel S, or one/more
> from [2345], but not both!
Actually no... that is correct/valid, but the initscript 'start' action
should not try to start something that is already running.
I can commit fixes for these 'soon', but for now here are some notes
before I forget:
nfsd tries to start twice because the --pidfile option is given but the
daemon doesn't really create one. On starting the second instance, it
returns status 0, forks to background then writes "Can't read stable
storage file" to syslog and aborts.
mountd doesn't start if /etc/exports doesn't exist; should probably
test for this in the initscript and then 'warn' rather than 'fail'.
rpc.statd doesn't create a pid file either so --pidfile causes two
processes to be started (and both stay running).
rpc.lockd tries twice to load but is failing due to #664812. If it did
work, it would try to run twice (again because of --pidfile) but fail
the second time due to address being in use.
Regards,
--
Steven Chamberlain
steven@pyro.eu.org
Reply to: