>As any modem-using x86 user must know by now, ttymon periodically
>dies. The live periods can be days, or, like today, hours, which can
>be very frustrating just when I have OpenWin set up the way I want it.
>The only way I've found to get the modem back to answering the phone
>is by rebooting the system. If there's another way, I'd certainly love
>to hear it!
>Thanks in advance.
On my Dell SVR4 2.2 box, the same problem exists with ttymon; I suspect
the problem lies in the original AT&T ttymon/sacadm/portmon code, as
I've seen complaints about just about every known port of SVR4 with
You may have two different problems:
1) The ttymon process actually dies.
2) The status of your service is "disabled."
In case 2, the ttymon process is still running, but the modem is offline,
DTR is low. For me, the pmadm utility is useful in re-enabling the
pmadm -e -p ttymon3 -s 02h
You will obviously have to change the arguments to -p and -s to fit your
Case 1 is a bit more problematic, but just a bit. You can tweak sacadm
to watch the ttymon process using the -n option. From the Dell sacadm
Set the restart count to count. If a restart count is not
specified, count is set to 0. A count of 0 indicates that
the port monitor is not to be restarted if it fails.
So, set the restart count to any positive restart count. I currently
use 3, but 5 or 10 or larger might be a good idea.
On the other hand, you might just disable ttymon for the serial port in
question, and use uugetty spawned from /etc/inittab, and totally avoid
the buggy SVR4 sacadm/portmon/ttymon code.