Bugzilla – Bug 968571
mgetty systemd configuration contains errors
Last modified: 2019-05-08 16:10:49 UTC
- 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
(In reply to Dieter Jurzitza from comment #0) > - both files /usr/lib/systemd/system/mgetty@.service and > /usr/lib/systemd/system/vgetty@.service have wrong permissions, causing > systemd to moan loudly Incorrect permission are minor issue, I will however update them. > - 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 ... /dev/modem is a symlink, mgetty needs real device to work properl (i.e mgetty@tty1).
This is an autogenerated message for OBS integration: This bug (968571) was mentioned in https://build.opensuse.org/request/show/362351 42.1+13.2 / mgetty
> https://build.opensuse.org/request/show/362351 42.1+13.2 / mgetty This has a review on Base:System / mgetty. Stanislav, could you please review and approve for maintenance?
Update with correct permissions is on the way.
openSUSE-RU-2016:0885-1: An update that has one recommended fix can now be installed. Category: recommended (moderate) Bug References: 968571 CVE References: Sources used: openSUSE Leap 42.1 (src): mgetty-1.1.36-62.1 openSUSE 13.2 (src): mgetty-1.1.36-55.7.1
*** Bug 972770 has been marked as a duplicate of this bug. ***
SUSE-RU-2019:1192-1: An update that has two recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1129954,968571 CVE References: Sources used: SUSE Linux Enterprise Server 12-SP4 (src): mgetty-1.1.36-58.6.1 SUSE Linux Enterprise Server 12-SP3 (src): mgetty-1.1.36-58.6.1 SUSE Linux Enterprise Desktop 12-SP4 (src): mgetty-1.1.36-58.6.1 SUSE Linux Enterprise Desktop 12-SP3 (src): mgetty-1.1.36-58.6.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.