[Bug 914661] New: Mgetty - no way to start mgetty service
http://bugzilla.opensuse.org/show_bug.cgi?id=914661 Bug ID: 914661 Summary: Mgetty - no way to start mgetty service Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: Other OS: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers@suse.de Reporter: wharms@bfs.de QA Contact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Fungus/8.0 (X11; U; C64 6510; de; 8bit) Build Identifier: I use mgetty as modem getty to start pppd on dial-in after the installation of mgetty there seems no way of making this service available. with SysV-init added a line into inittab but i could not find a working way with systemd (or a documentation) the yast2 modem module seems to allow dialout only. Reproducible: Always Expected Results: After installation the should be something that tell one what do to next -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=914661
Martin Pluskal
http://bugzilla.opensuse.org/show_bug.cgi?id=914661
--- Comment #2 from a b
http://bugzilla.opensuse.org/show_bug.cgi?id=914661
Martin Pluskal
http://bugzilla.opensuse.org/show_bug.cgi?id=914661
--- Comment #4 from Martin Pluskal
please add some documentation how to handle more that one modem/mgetty thx
For each modem/device you want to handle just start/enable mgetty@X.service, where X is device which is supposed to be used (ttyS0 or ttACM0 or whatever you need). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=914661
a b
http://bugzilla.opensuse.org/show_bug.cgi?id=914661
Martin Pluskal
I did rpm -U mgetty-1.1.36-84.1.x86_64.rpm * systemctl start mgetty@modem.service -- never returns
$ systemctl enable mgetty@modem.service ln -s '/usr/lib/systemd/system/mgetty@.service' '/etc/systemd/system/getty.target.wants/mgetty@modem.service'
but no mgetty to find with ps
note; i have tested /dev/modem by using minicom, it works
Ah I see, /dev/modem is symlink to /dev/ttyX, but this will not work with unit due to other reasons (feel free to look at unit file) - you should use systemctl start mgetty@ttyX.service. Even if service fails to start, systemctl start mgetty@X.service should (and will) finish after some time (several minutes). After that you can see what happened via "systemctl status mgetty@X.service". -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=914661
--- Comment #7 from Martin Pluskal
http://bugzilla.opensuse.org/show_bug.cgi?id=914661
--- Comment #8 from a b
http://bugzilla.opensuse.org/show_bug.cgi?id=914661
Martin Pluskal
systemctl status mgetty@ttyS6 mgetty@ttyS6.service - mgetty on /dev/ttyS6 Loaded: loaded (/usr/lib/systemd/system/mgetty@.service; enabled) Active: active (running) since Mo 2015-01-26 15:23:39 UTC; 54s ago Docs: man:mgetty(8) Main PID: 17622 (mgetty) CGroup: /system.slice/system-mgetty.slice/mgetty@ttyS6.service └─17622 /usr/sbin/mgetty /dev/ttyS6
ttyS6 works for me. Thanks for confirmation, I will request maintenance update.
why is the symlink to /dev/modem a problem ?
There is BindsTo=dev-%i.device in unit file related to device, where /dev/modem is afaik not considered to be device by udev/systemd (although symlink is generated by udev). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=914661
Martin Pluskal
http://bugzilla.opensuse.org/show_bug.cgi?id=914661
Benjamin Brunner
http://bugzilla.opensuse.org/show_bug.cgi?id=914661
Tomáš Chvátal
participants (1)
-
bugzilla_noreply@novell.com