Package: systemd
Version: 36-0.1
Hi,
I get the following line in dmesg on bootup:
[ 15.852509] systemd[1]: [/etc/init.d/lvm2:3] Failed to add LSB
Provides name lvm.service, ignoring: File exists
Uninstalling schroot makes it go away. By adding a few log_debug()
lines, we discover this EEXIST comes from the following condition
tripping in unit_add_name():
if ((r = hashmap_put(u->meta.manager->units, s, u)) < 0) {
and earlier in the debug log we find
[ 15.766682] systemd[1]: Failed to load configuration for
lvm.service: No such file or directory
which is presumably triggered by schroot's
# Should-Start: lvm
Known problem? Any ideas for tracking it down? LSB headers for lvm2 and
schroot follow.
Thanks,
Jonathan
-- >8 -------- from lvm2 2.02.86-1 --------- >8 --
#!/bin/sh
### BEGIN INIT INFO
# Provides: lvm2 lvm
# Required-Start: mountdevsubfs
# Required-Stop:
# Should-Start: udev mdadm-raid cryptdisks-early multipath-tools-boot
# Should-Stop: umountroot mdadm-raid
# X-Start-Before: checkfs mountall
# X-Stop-After: umountfs
# Default-Start: S
# Default-Stop:
### END INIT INFO
-- 8< ------------------------------------- 8< --
-- >8 -------- from schroot 1.5.0-1 ------- >8 --
#! /bin/sh
#
### BEGIN INIT INFO
# Provides: schroot
# Required-Start: $local_fs $syslog $network $remote_fs
# Required-Stop:
# Should-Start: lvm
# Should-Stop:
# Default-Start: S
# Default-Stop:
# Short-Description: Recover schroot sessions.
# Description: Activate any persistent sessions after a reboot.
# Setup scripts will be run to mount filesystems and
# bring the chroot back to a working state.
### END INIT INFO
-- 8< ------------------------------------ 8< --
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
