On Fri, Jan 11, 2019 at 9:39 AM Dmitry Bogatov <[email protected]> wrote:
> > [2019-01-01 22:38] Dmitry Bogatov <[email protected]> > > [2018-12-29 19:51] Michael Biebl <[email protected]> > > > Am 29.12.18 um 19:34 schrieb Dmitry Bogatov: > > > > control: reassign -1 init-system-helpers > > > > > > How should we handle bugs that are really sysvinit specific, even if > > > they affect update-rc.d/invoke-rc.d (i.e. init-system-helpers) > > > > > > No one of the current init-system-helpers is using sysvinit anymore, so > > > bug reports like this one are bound to get forgotten/ignored. > > > > Quite unfortunate situation. Okay, I will take a look at it myself. > > > > > Should we usertag them somehow so those sysvinit specific issues are > > > on the radar on the sysvinit maintainers? This really needs a > > > fix/patch from someone actively using sysvinit. > > > > Just added usertag. > > Okay. I believe this bug could be closed on timeout, and both 'start' > and 'stop' sub-actions could be dropped, together with `sysv_plain' > (pre-boot-dependency) part. > They are already mapped to `defaults` > > What worries me is that `update-rc.d defaults' do not seems to > work (insserv=1.18.0): > > # update-rc.d cron disable 3 > insserv: warning: current start runlevel(s) (2 4 5) of script `cron' > overrides LSB defaults (2 3 4 5). > insserv: warning: current stop runlevel(s) (3) of script `cron' > overrides LSB defaults (empty). > # update-rc.d cron defaults > insserv: warning: current start runlevel(s) (2 4 5) of script `cron' > overrides LSB defaults (2 3 4 5). > insserv: warning: current stop runlevel(s) (3) of script `cron' > overrides LSB defaults (empty). > # insserv cron > insserv: warning: current start runlevel(s) (2 4 5) of script `cron' > overrides LSB defaults (2 3 4 5). > insserv: warning: current stop runlevel(s) (3) of script `cron' > overrides LSB defaults (empty). > # insserv cron -f > insserv: warning: current start runlevel(s) (2 4 5) of script `cron' > overrides LSB defaults (2 3 4 5). > insserv: warning: current stop runlevel(s) (3) of script `cron' > overrides LSB defaults (empty). > # update-rc.d cron enable 3 > > As can be seen, neither `update-rc.d defaults' nor direct invocation of > /sbin/insserv do not restore runlevels, prescribed by LSB header. Jesse, > am I doing it wrong? To preserve admin modifications, `update-rc.d defaults` must not touch any existing links. That's documented in the manpage: > If any files named /etc/rcrunlevel.d/[SK]??name already exist then update-rc.d does nothing. -- Saludos, Felipe Sateler
_______________________________________________ Pkg-systemd-maintainers mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
