[2019-04-12 01:32] Mathieu Mirmont <m...@parad0x.org>
> Package: bcron
> Version: 0.11-8
> Severity: important
>
> Dear Maintainer,
>
> The bcron package provides both init.d scripts and runit services.
> When installing it in a system where runsvdir is running (for instance
> via runit-init or runit-sysv), then the daemons are started by both
> runsvdir and by update-rc.d:
>
> $ pstree
> bash-+-daemon---bcron-update
> |-daemon---bcron-sched---bcron-exec
> |-daemon---unixserver
> |-pstree
> `-runsvdir-+-runsv-+-bcron-update
> | `-svlogd
> |-runsv-+-svlogd
> | `-unixserver
> `-runsv-+-bcron-sched---bcron-exec
> `-svlogd
>
> This issue is most likely present in all packages that ship both
> init.d scripts and runit services, I aritrarily picked bcron to report
> the bug, please feel free to re-assign.
No, usual behaviour in this case is that init.d script is started first,
and runscript is keep trying to start daemon too, but fails, since
daemon refuses to start second instance of itself. It is no good too, of
course.
I believe this bug will be fixed as effect of #924769 (not marked as
resolved, due my typo in changelog), which is now in Archives as
runit=2.1.2-28/experimental. With #924769 in effect, runscript will stop
init.d instance before starting its own. Mind to check?
> I suspect that a fix could be implemented in invoke-rc.d by making it
> aware of runsvdir, similarly to how it is already aware of systemd and
> openrc?
Yes, it is planned, but pushing changes to init-system-helpers is quite
long and painful process for me for social reasons. If you are willing
to help, you are more then welcome. Take a look at #924132.
--
Note, that I send and fetch email in batch, once every 24 hours.
If matter is urgent, try https://t.me/kaction
--
