I wrote:
> It [lock] is in the distributed options file.
Hamish writes:
> Ahh, that's probably it then. It's not in my options file, because my
> setup is rather customised because I use diald for one link.
> I have two other /etc/ppp/peers/ files which have the lock
> option in them, though, cr
On Sat, May 01, 1999 at 07:56:35AM -0500, John Hasler wrote:
> Madarasz Gergely writes:
> > do you have an option "lock" to pppd ? it should be in peers/isp or in
> > the options file.
>
> It is in the distributed options file.
Ahh, that's probably it then. It's not in my options file, because my
Madarasz Gergely writes:
> do you have an option "lock" to pppd ? it should be in peers/isp or in
> the options file.
It is in the distributed options file.
--
John Hasler
[EMAIL PROTECTED] (John Hasler)
Dancing Horse Hill
Elmwood, WI
On Sat, 1 May 1999, Hamish Moffatt wrote:
> On Sat, May 01, 1999 at 01:07:53PM +0200, Gergely Madarasz wrote:
> > On Sat, 1 May 1999, Hamish Moffatt wrote:
> > > Is there a workaround? It's most annoying and has been bugging me for a
> > > while.
> >
> > Are you sure you use the same device file
On Sat, May 01, 1999 at 01:07:53PM +0200, Gergely Madarasz wrote:
> On Sat, 1 May 1999, Hamish Moffatt wrote:
> > Is there a workaround? It's most annoying and has been bugging me for a
> > while.
>
> Are you sure you use the same device file name for both mgetty and pppd ?
> I mean /dev/ttyS1 fo
On Sat, 1 May 1999, Hamish Moffatt wrote:
> I'm having some weird interaction between mgetty and pppd/chat.
> I have mgetty running on a couple of modems. When I dialout (pon),
> I start getting error messages from mgetty in the log, like
>
> 05/01 20:47:09 yS1 mdm_read_byte: read returned 0: Su
I'm having some weird interaction between mgetty and pppd/chat.
I have mgetty running on a couple of modems. When I dialout (pon),
I start getting error messages from mgetty in the log, like
05/01 20:47:09 yS1 mdm_read_byte: read returned 0: Success
05/01 20:47:09 yS1 wfr: error in read(): Succe
7 matches
Mail list logo
