mgetty-1.1.9 on Solaris2.5.1/Sparc

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Sorry for my misposting .... err, posting in undesired language.
So please let me have a second try - in english. In the hope, one of you
might have a solution for me.

Now I have installed mgetty on Solaris. It works fine for incoming calls
using simple login, UUCP or fax transfers. This works wether I use
/dev/ttyb, /dev/cua/b (compilant to a hint in the mgetty-FAQ) or a selfmade
link /dev/cuab which points to cua/b .

Afterwards I tried to get minicom-1.75 running. In standalone use, without
having mgetty sitting on the modem port, minicom does everything I want 'em
to do, but as soon as I put mgetty to listen on the port using an entry in
/etc/inittab:

d1:23:respawn:/usr/local/sbin/mgetty -x 5 -n 1 /dev/cua/b


.... minicom hardly can send or recieve any charater to or from the modem.
It takes more than 10 seconds to drop an AT-command. In my knowledge mgetty
leaves the modem port to another program as long as it finds a lockfile in
the correct directory corresponding to an existing PID. So when I have a
look at an mgetty lockfile:

 5567


.... and a minicom lockfile:

 5566 minicom martin


.... then I can't see any reason why mgetty should prevent minicom from
using the serial port. I thought the lockfile is correct as long as the PID
ends on the 10th character. And why is sendfax working without any problem ?

Martin.
-- 
 Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------
.