Bug ID 968571
Summary mgetty systemd configuration contains errors
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 ---

- both files /usr/lib/systemd/system/mgetty@.service and
/usr/lib/systemd/system/vgetty@.service have wrong permissions, causing systemd
to moan loudly
- when creating a link containing a device name (say, mgetty@modem.service ->
mgetty@.service a device file dev-modem is requested, but does not exist, nor
exists an example how this ought to look like, and, honestly speaking, I do not
know what this file would be worth for ...

- please note, the device /dev/modem exists on my system!

Feb 27 21:05:32 djunix systemd[1]: Job dev-modem.device/start timed out.
Feb 27 21:05:32 djunix systemd[1]: Timed out waiting for device
dev-modem.device.
-- Subject: Unit dev-modem.device has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit dev-modem.device has failed.
-- 
-- The result is timeout.
Feb 27 21:05:32 djunix systemd[1]: Dependency failed for mgetty on /dev/modem.
-- Subject: Unit mgetty@modem.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit mgetty@modem.service has failed.


It would be kind someone could take a look and fix this,
thank you 
take care




Dieter Jurzitza


You are receiving this mail because: