mgetty-1.1.9 on Solaris2.5.1/Sparc

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

Hi,

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

Sounds fine, so far.

> .... 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

Hmmm, that is not really a proper uucp style lock file (the format is
"%10d\n"), but I think mgetty should be able to handle that.

So, how does the mgetty log file look like?

> .... 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 ?

... let's check the log files for hints what's going on.

gert

-- 
USENET is *not* the non-clickable part of WWW!
           //www.muc.de/~gert/
Gert Doering - Munich, Germany      gert@greenie.muc.de
fax: +49-89-35655025    gert.doering@physik.tu-muenchen.de
.