Dialin/out mgetty in IRIX 6.5

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

Gert Doering wrote:

> Hi,
>
> (I'm copying the mgetty list on this - there are IRIX users out there)

Hello.
Thanks for you reply.

Here below more information about my setup.

The program for dial out is either /usr/etc/ppp or /usr/bin/cu, so not
self-compiled ones.

In fact, Irix should be SVR4, so it positevely  should use the
LK.<device major>.<device minor>.<inode number> filename construction for
the locks.

Unfortunately, and that probably is the focus of the problem, from the man
page of the cu/ppp command I got:

FILES
     /etc/uucp/Systems
     /etc/uucp/Devices
     /var/spool/locks/LCK..(tty-device)
     /dev/tty*

That's equivalent to say  that Irix uses the non-SVR4 strategy for typical
system dial out program, while behaves straight SVR4 on other respects.

I've tried to recompile without the -Dsgi or changing it to -DSVR3, but the
behaviour is still the same, that I say again below:

While in waiting for a call state, dialin out happens to produce characters
on the line, fact that in turn misleads mgetty to believe that a call is
incoming (it actually waits for a RING that never comes), until it times out
claiming junk on the line.

As to the Irix users already running with success, could please anyone of
them confirm that their configuration is a dialin/dialout one? Just running
mgetty in dialin only mode is fine in my case.

Also, I've tried to subscribe to the mgetty@muc.de list, but with no success
- the mailer daemon replies that only the fc-bayern and linux-ha lists are
defined on the server. Thanks for this help as well!

Best regards, Marco

>
> On Fri, May 07, 1999 at 09:34:08AM +0200, Marco Masotti wrote:
> > Mgetty (even the latest version) seems to ignore the lock files ,
> > although I'm pretty sure the  locks directory is correct.
>
> Definitely not.  You just have to make sure that all programs agree
> on the name of the lock files...
>
> > What mgetty actually does is to ignore the LCK.ttyf2 lock file created
> > by the dial-out program, and comes across with its own file, like
> > LK.000.000.0.091, trying to answer an incoming call while it has to let
> > another one to call out instead.
>
> This is a typical file name mismatch - on SVR4, the naming convention
> for lock files is LK.<device major>.<device minor>.<inode number>
> or something like that, while on other systems, the name of the
> device is used for the lock file name (LCK..tty<x>).
>
> Now I don't know IRIX, but it seems to define SVR4 in its C compiler, so
> mgetty picks the lock file type for SVR4 - and your unnamed dial-out
> program uses SVR3 locking strategy.  Is this dial-out program something
> you have compiled yourself?  If yes, change this to SVR4 style locking
> - if no, find out why IRIX is #define'ing SVR4 and then teach mgetty
> to not use SVR4 style locking...
>
> As I didn't get any Irix trouble reports yet, I guess that this is
> a compiled-yourself dial-out program, and using system tools (like
> "cu -l ttyf2") would work fine.
>
> gert
>
> --
> Gert Doering
> Mobile communications ... right now writing from *AWAY* :-))
> ... mobile phone: +49 177 2160221 ... or mail me:  gert@greenie.muc.de