Bug ID | 968573 |
---|---|
Summary | systemd fails on symlink |
Classification | openSUSE |
Product | openSUSE Distribution |
Version | Leap 42.1 |
Hardware | Other |
OS | Other |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | Basesystem |
Assignee | bnc-team-screening@forge.provo.novell.com |
Reporter | dieter.jurzitza@t-online.de |
QA Contact | qa-bugs@suse.de |
Found By | --- |
Blocker | --- |
If I create a symlink: systemd@modem.service -> modem@.service the unit - file fails badly: djunix:/usr/lib/systemd/system # ln -s mgetty@.service mgetty@modem.service djunix:/usr/lib/systemd/system # la mgetty@modem.service lrwxrwxrwx 1 root root 15 27. Feb 21:23 mgetty@modem.service -> mgetty@.service djunix:/usr/lib/systemd/system # systemctl enable mgetty@modem.service Failed to execute operation: No such file or directory the same with a hard link: djunix:/usr/lib/systemd/system # ln mgetty@.service mgetty@modem.service djunix:/usr/lib/systemd/system # systemctl enable mgetty@modem.service -> simply works. I'd consider this a bug as the documentation states that "typically the unit file is created as a symlink pointing to the @.service - File. Thank you for looking into this, take care Dieter Jurzitza