[Bug 968573] New: systemd fails on symlink
http://bugzilla.opensuse.org/show_bug.cgi?id=968573 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 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=968573
http://bugzilla.opensuse.org/show_bug.cgi?id=968573#c1
--- Comment #1 from Dieter Jurzitza
http://bugzilla.opensuse.org/show_bug.cgi?id=968573
Martin Pluskal
http://bugzilla.opensuse.org/show_bug.cgi?id=968573
http://bugzilla.opensuse.org/show_bug.cgi?id=968573#c2
Bernhard Wiedemann
http://bugzilla.opensuse.org/show_bug.cgi?id=968573
http://bugzilla.opensuse.org/show_bug.cgi?id=968573#c3
--- Comment #3 from Dieter Jurzitza
does the added symlink maybe need a systemctl daemon-reload to be seen?
No, no change in behaviour. Given that I am using a symlink, the error - message is always the same, no matter wheter or not I applied a systemctl daemon-reload before or not. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=968573
http://bugzilla.opensuse.org/show_bug.cgi?id=968573#c4
--- Comment #4 from Dieter Jurzitza
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
I just discovered that I used wrong names, it must say: If I create a symlink: mgetty@modem.service -> mgetty@.service sorry for the misleading typo .... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=968573
http://bugzilla.opensuse.org/show_bug.cgi?id=968573#c5
Christian Boltz
http://bugzilla.opensuse.org/show_bug.cgi?id=968573
http://bugzilla.opensuse.org/show_bug.cgi?id=968573#c6
--- Comment #6 from Dieter Jurzitza
http://bugzilla.opensuse.org/show_bug.cgi?id=968573
http://bugzilla.opensuse.org/show_bug.cgi?id=968573#c7
--- Comment #7 from Martin Pluskal
Could you kindly shed some light on this, too? Things are going well if I delete the reference to BindsTo=dev-%i.device from within mgetty@service, so, "ttyS4" is acceptable, a link "modem->ttyS4" is not? How would I ensure the apropriate device to get selected?
Thanks again - and, finally, could someone provide a pointer where to get this information from? The documentation is difficult to seek for this. It means that it depends on said device (i.e. ttyS4), while /dev/modem is I assume not considered as a device: I guess that while "systemctl status dev-ttyS4.device" will show you something like: ● dev-ttyS4.device - /dev/ttyS4 Follow: unit currently follows state of sys-devices-platform-serial8250-tty-ttyS4.device Loaded: loaded Active: active (plugged) since Sat 2016-02-27 11:20:32 CET; 1 day 9h ago Device: /sys/devices/platform/serial8250/tty/ttyS4
"systemctl status dev-modem.device" will not -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=968573
http://bugzilla.opensuse.org/show_bug.cgi?id=968573#c8
--- Comment #8 from Dieter Jurzitza
http://bugzilla.opensuse.org/show_bug.cgi?id=968573 http://bugzilla.opensuse.org/show_bug.cgi?id=968573#c9 --- Comment #9 from Martin Pluskal--- (In reply to Dieter Jurzitza from comment #8) > You are totally right. So, my initial procedure was wrong, causing the error > message with the symlink - I guess there were two symlinks at the end of the > day, messing up. > > However, I see no way to cope with the modem device on boot but to use a > symlink. If someone switches the connector and reboots, he is currently > forced to reassign the device name in order to restart mgetty on the right > device file. 1) Does this happen ofthe (switching of cables)? 2) Perhaps you could enable mgetty for all serial devices ... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=968573
http://bugzilla.opensuse.org/show_bug.cgi?id=968573#c10
--- Comment #10 from Dieter Jurzitza
http://bugzilla.opensuse.org/show_bug.cgi?id=968573
http://bugzilla.opensuse.org/show_bug.cgi?id=968573#c11
Bernhard Wiedemann
What do you think about a feature request upstream to make /usr/lib/systemd/system/dm-event.socket work on softlinks to devices?
Thank you for every input. Take care
giving that question to device-mapper package maintainer. I also think, that symlinks could simplify such tasks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=968573
http://bugzilla.opensuse.org/show_bug.cgi?id=968573#c12
--- Comment #12 from Dieter Jurzitza
http://bugzilla.opensuse.org/show_bug.cgi?id=968573
http://bugzilla.opensuse.org/show_bug.cgi?id=968573#c13
Bernhard Wiedemann
http://bugzilla.opensuse.org/show_bug.cgi?id=968573
http://bugzilla.opensuse.org/show_bug.cgi?id=968573#c20
--- Comment #20 from Dieter Jurzitza
http://bugzilla.opensuse.org/show_bug.cgi?id=968573
http://bugzilla.opensuse.org/show_bug.cgi?id=968573#c22
--- Comment #22 from Dieter Jurzitza
http://bugzilla.opensuse.org/show_bug.cgi?id=968573
http://bugzilla.opensuse.org/show_bug.cgi?id=968573#c23
Dieter Jurzitza
From there I can probably see how complex things turn out to be. Take care
Dieter Jurzitza -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=968573
http://bugzilla.opensuse.org/show_bug.cgi?id=968573#c25
Dieter Jurzitza
participants (1)
-
bugzilla_noreply@novell.com