Some good news, the current LTS release of Ubuntu server is running the 
Ubuntu/Debian distribution of mgetty just fine (info below). Mgetty now 
respawns (doesn't hang) like it did with 12.04 (described above). 

I suspect the problem was with Upstart all along, however, the mgetty
package in 14.04 LTS is an update from the one used in the the 12.04 LTS
release.

http://packages.ubuntu.com/trusty/mgetty
http://packages.ubuntu.com/precise/mgetty

Luke

root@somewhere:/var/log/mgetty# uname -a
Linux somewhere 3.13.0-35-generic #62-Ubuntu SMP Fri Aug 15 01:58:42 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

root@somewhere:/var/log/mgetty# lsb_release -a
No LSB modules are available.
Distributor ID:    Ubuntu
Description:    Ubuntu 14.04.1 LTS
Release:    14.04
Codename:    trusty

root@somewhere:/var/log/mgetty# initctl --version
initctl (upstart 1.12.1)
Copyright (C) 2006-2014 Canonical Ltd., 2011 Scott James Remnant

root@somewhere:/var/log/mgetty# apt-cache show mgetty
Package: mgetty
Priority: extra
Section: universe/comm
Installed-Size: 369
Maintainer: Ubuntu Developers <[email protected]>
Original-Maintainer: Andreas Barth <[email protected]>
Architecture: amd64
Version: 1.1.36-2ubuntu1

root@somewhere:/var/log/mgetty# dmesg | grep tty
[    0.000000] console [tty0] enabled
[    0.874880] 0000:37:09.0: ttyS4 at I/O 0xe080 (irq = 21, base_baud = 921600) 
is a 16550A
[    0.895245] 0000:37:09.0: ttyS5 at I/O 0xe088 (irq = 21, base_baud = 921600) 
is a 16550A
[14326.348920] init: ttyS4 main process ended, respawning
[14573.114758] init: ttyS4 main process (2530) terminated with status 10

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/990680

Title:
  mgetty won't timeout (gets hung) after MODEM hangup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mgetty/+bug/990680/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to