control: tags -1 +help +moreinfo
[2019-07-17 13:25] Lorenzo Puliti <[email protected]> > [...] > insserv: Script rsync has overlapping Default-Start and Default-Stop > runlevels (2 3 4 5) and (2 3 4 5). This s > hould be fixed. > insserv: Script lvm2 has overlapping Default-Start and Default-Stop runlevels > (S) and (S). This should be fixe > d. > insserv: Script apparmor has overlapping Default-Start and Default-Stop > runlevels (S) and (S). This should be > fixed. > [...] > I'm not sure why it detects that start and stop runlevels are overlapping, > all rsync lvm2 and apparmor > have empty 'Default-Stop' field in the header like this > > ### BEGIN INIT INFO > # Provides: apparmor > # Required-Start: $local_fs > # Required-Stop: umountfs > # Default-Start: S > # Default-Stop: > # Short-Description: AppArmor initialization Are there overrides in /etc/insserv/overrides/? Does this warning appear if you invoke: 1. # insserv 2. # insserv apparmor 3. If either 1. or 2. reproduces problem, please invoke them under strace and show output. > Downgrading insserv to 1.18.0-2 fix the issue for me Sure, this check was introduced in 1.20 (a06c7fae, to be exact). -- Note, that I send and fetch email in batch, once in a few days. Please, mention in body of your reply when you add or remove recepients.
