control: tags -1 + moreinfo Am 08.01.2015 um 21:55 schrieb Daniel Dickinson: > Package: systemd > Version: 215-8 > Severity: important > > I've had to (at least temporarily) switch to sysvinit because systemd fails > to start old-style initscripts on some of my systems. I don't have the time > at present to debug mostly because with systemd I have no idea where to even > start troubleshooting and I need my systems to work *now* not three weeks or > three months from now. (These are systems I use for doing paid work, so there > is not option to leave them in a broken state to debug).
Which init scripts do fail to start? Can you past the output of systemctl status <foo.service> for those failing services and the output journalctl -alb You can keep sysvinit-core install. Just make sure systemd is installed and boot with "init=/bin/systemd" on the kernel command line to temporarily switch the active init. Without further information, there is unfortunately not a lot we can do. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
