[2847] in linux-net channel archive
Re: co-existance of pppd and mgetty ?
daemon@ATHENA.MIT.EDU (Johan =?iso-8859-1?Q?Myr=E9en?=)
Thu May 9 21:17:31 1996
Date: Thu, 9 May 1996 10:28:47 +0300 (EET DST)
From: Johan =?iso-8859-1?Q?Myr=E9en?= <jem@vistacom.fi>
To: Chris Bagwell <cbagwell@rockdal.aud.alcatel.com>
cc: linux-ppp@vger.rutgers.edu, linux-net@vger.rutgers.edu,
ajcurtis@westworld.com
In-Reply-To: <9605071810.AA18741@mwsun001.aud.alcatel.com>
On Tue, 7 May 1996, Chris Bagwell wrote:
> By default, they are both attempting to put a lock file in two different locations
> so mgetty never see's pppd using the modem and so it hangs it up and resets.
> This is from memory since I'm not at home but mgetty places it at
> /var/spool/uucp/LCK..?? and ppd places it at /var/lock/LCK..??
> You can either change mgetty's config files or a file in pppd and recompile.
> I did it in pppd since I already had mgetty set up. The file in pppd
> is "sys-linux.c". Change the line with /var/lock/LCK to /var/spool/uucp/LCK
> and then recompile.
No, change mgetty to use /var/lock instead, that's the correct directory
according to the Linux File System Standard. The easiest way is to make
/var/spool/uucp a link to /var/lock.
> It would be nice if the location of the locking string was mentioned in the
> pppd documention (I've never seen it but I didn't look real hard).
On the contrary, since pppd gets it right, I think it is good pppd hides that
information, making it harder to break it. You are not supposed to change the
lock directory name.
Note that you'll have to use /dev/ttyS* (not /dev/cua*) for both mgetty and
pppd, otherwise you will still have the same problem with differently
named lock files.
Johan Myreen
jem@iki.fi
