>
>
> >Synopsis: rc.subr: spurious "kill: <pid>: no such process" on start
> with rc_bg=YES
>
> When starting a package daemon whose rc.d script sets rc_bg=YES,
> the following message is sometimes printed at boot:
> The daemon starts correctly and "rcctl check oficina" reports ok,
> so the problem is cosmetic.
>
Not just cosmetic.
> With rc_bg=YES, rc_start returns immediately. If rc_check already
> succeeds inside _rc_wait_for_start, the loop breaks, the subshell
> runs "pkill -ALRM -P $$" and exits, so the later
> "kill -ALRM ${_TIMERSUB}" targets a process that no longer exists
> and prints an error.
> - kill -ALRM ${_TIMERSUB}
> + kill -ALRM ${_TIMERSUB} 2>/dev/null
I am not talking for the project, but I am quite certain that trying to
kill the wrong process is what needs to be fixed, not silencing that it
happens.
What will the system do if the PID got reused in that time span?
--
May the most significant bit of your life be positive.
