Okan Demirmen
2005-12-09 14:04:25 UTC
hi all -
so i understand the issue with mgetty complaining loudly if the modem is
either turned off or missing. so if one has mgetty listening without the
modem, it will forever try to talk to it.
ok, but the issue i'm having is that when i send a kill signal to
mgetty, it never releases its lock(s) and this becomes a problem while
trying to reboot/shutdown - actually, it's the umount'ing bit that
hurts. it doesn't matter if init sends the signal or one does so
manually, mgetty doesn't really go away. at most, it will go into IE
(idle and trying to exit). the only way to get it to die (even after
sending kill signals) is to breify turn on the modem.
is there something i'm missing here?
for the record, this is mgetty 1.1.34 on openbsd -current (and 3.8) with
an external courier v.everything modem.
thanks,
okan
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
so i understand the issue with mgetty complaining loudly if the modem is
either turned off or missing. so if one has mgetty listening without the
modem, it will forever try to talk to it.
ok, but the issue i'm having is that when i send a kill signal to
mgetty, it never releases its lock(s) and this becomes a problem while
trying to reboot/shutdown - actually, it's the umount'ing bit that
hurts. it doesn't matter if init sends the signal or one does so
manually, mgetty doesn't really go away. at most, it will go into IE
(idle and trying to exit). the only way to get it to die (even after
sending kill signals) is to breify turn on the modem.
is there something i'm missing here?
for the record, this is mgetty 1.1.34 on openbsd -current (and 3.8) with
an external courier v.everything modem.
thanks,
okan
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de