Am 06.01.2013 16:43, schrieb Christian Boltz:
Hello,
Am Sonntag, 6. Januar 2013 schrieb Stefan Seyfried:
susi:~ # rcsyslog start redirecting to systemctl start syslog Failed to issue method call: Unit syslog.service failed to load: No such file or directory. See system logs and 'systemctl status syslog.service' for details. susi:~ # systemctl status syslog.service syslog.service Loaded: error (Reason: No such file or directory) Active: inactive (dead)
So we should be honest and drop it.
Sounds like https://bugzilla.novell.com/show_bug.cgi?id=790805
Symptom: /etc/systemd/system/multi-user.target.wants/syslog.service is a broken symlink pointing to a non-existant file.
Solution: systemctl enable rsylsog.service (or whatever syslog you prefer)
Thanks, that actually helped (with syslog-ng.service in my case).
Better solution: get a working upgrade path that automatically fixes the symlink
Absolutely necessary IMVHO. I mean -- i'm really systemd-friendly, but that everything gets broken all the time by the systemd migration and nobody cares for fixing it up is really annoying and makes me want to stop using it as in real life the benefits of systemd vs. sysvinit are nothing that you'd notice as a normal user. Thanks again, Stefan -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org