> Have you cranked up the debug level in the config
> file? Are the
> messages you posted in syslog or the var/log/mgetty-* file?
Yes, I tried cranking up the debug level. I got even more
messages with "No such file or directory" at the end of them.
The messages I posted are in syslog. The new
t: September 14, 2000 1:05 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Problem with mgetty-1.1.22-1.5.x.i386.rpm
>
>
> The issue with using /dev/modem or /dev/ttyS2 is with
> sharing. You just
> have to be consistant with which one you use, because
> if you mix and
> match,
The issue with using /dev/modem or /dev/ttyS2 is with sharing. You just
have to be consistant with which one you use, because if you mix and
match, each seperate program will not "place nice" with the others. If you
use the smae name across the board, then they will cooperate with each
other (as b
"Owen V. Gray" wrote:
> No, I don't use a /dev/modem symlink. The mgetty documentation
> recommends against using it, and mgetty-1.1.14 works fine using
> /dev/ttyS2 directly. I've looked at the documentation for the new
> version, and it does not seem to have changed in this regard.
>
> Is there
dhat-added patches that now
requires this?
Owen
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Bret Hughes
> Sent: September 13, 2000 4:47 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Problem with mgetty-1.1.22-1.5.x.i386.rpm
>
&g
"Owen V. Gray" wrote:
> I had mgetty-1.1.14-5 working fine on my RH5.2 system.
>
> I updated to mgetty-1.1.22-1.5.x.i386.rpm, and got the following
> in my logs:
>
> Sep 13 10:23:52 medarb mgetty[20714]: mgetty: experimental test
> release 1.1.22-Aug17: Success
> Sep 13 10:23:52 medarb mgetty[207
