[Touch-packages] [Bug 1431107] Re: ordering cycles with early boot rcS scripts with inappropriate rc2.d links

2015-03-31 Thread Martin Pitt
I can't fix that in general, as I don't know what causes these invalid rc2.d/ to rc5.d/ links with rcS init scripts. But for /etc/init.d/lvm2 in particular we can avoid running this pointless dummy script at all, I committed a change for this. ** Changed in: systemd (Ubuntu) Status:

[Touch-packages] [Bug 1431107] Re: ordering cycles with early boot rcS scripts with inappropriate rc2.d links

2015-03-18 Thread Daniel Serpell
I have the same problem with udev, screen-cleanup and udev-finish daniel@daniel-vaio:~$ grep Default-Start.*S /etc/rc[0-9].d/S0* /etc/rc2.d/S01udev:# Default-Start: S /etc/rc2.d/S02screen-cleanup:# Default-Start: S /etc/rc2.d/S02udev-finish:# Default-Start: S

[Touch-packages] [Bug 1431107] Re: ordering cycles with early boot rcS scripts with inappropriate rc2.d links

2015-03-16 Thread Benedikt
$ systemctl show --no-pager -p After apparmor After=system.slice systemd-journald.socket local-fs.target and: $ systemctl list-dependencies local-fs.target local-fs.target ● ├─-.mount ● ├─boot-efi.mount ● ├─home.mount ● ├─systemd-fsck-root.service ● └─systemd-remount-fs.service I think this is

[Touch-packages] [Bug 1431107] Re: ordering cycles with early boot rcS scripts with inappropriate rc2.d links

2015-03-16 Thread Benedikt
Hi Martin, I think I can reproduce the appaprmor failure on every boot: $ systemctl status apparmor.service -l ● apparmor.service - LSB: AppArmor initialization Loaded: loaded (/etc/init.d/apparmor) Active: failed (Result: exit-code) since So 2015-03-15 22:42:54 CET; 12h ago Docs:

[Touch-packages] [Bug 1431107] Re: ordering cycles with early boot rcS scripts with inappropriate rc2.d links

2015-03-13 Thread Manglasape
No, I only had these link, probably mine is another issue. It may be a disk failure, I'm trying a lot of distros lately. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

Re: [Touch-packages] [Bug 1431107] Re: ordering cycles with early boot rcS scripts with inappropriate rc2.d links

2015-03-12 Thread Martin Pitt
Manglasape [2015-03-12 23:56 -]: Mmmm I'm having a similar issue, but after ls -l /etc/rc*/*lvm2* I have 1rwxrwxrwx 1 root root 14 mar 8 19:43 /etc/rcS.d/S08lvm2- ../init.d/lvm2. I am not sure, does that means that I only have the symlink in rcS.d? Yes, that looks fine then. Which links

[Touch-packages] [Bug 1431107] Re: ordering cycles with early boot rcS scripts with inappropriate rc2.d links

2015-03-12 Thread Michael Marley
That seems to make everything work OK on bootup. Thanks! I have no idea how those symlinks got there. I definitely didn't put them there manually. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1431107] Re: ordering cycles with early boot rcS scripts with inappropriate rc2.d links

2015-03-12 Thread Manglasape
Mmmm I'm having a similar issue, but after ls -l /etc/rc*/*lvm2* I have 1rwxrwxrwx 1 root root 14 mar 8 19:43 /etc/rcS.d/S08lvm2- ../init.d/lvm2. I am not sure, does that means that I only have the symlink in rcS.d? Btw I am using Kubuntu vivid. -- You received this bug notification because you