*BSD News Article 42490


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!uwm.edu!vixen.cso.uiuc.edu!usenet.ucs.indiana.edu!pi
From: pi@indiana.edu (Raymond L. Gilbert)
Newsgroups: comp.os.386bsd.questions
Subject: Re: does kermit drop the line when exiting?
Date: 15 Feb 1995 09:52:03 GMT
Organization: A FreeBSD Enthusiast
Lines: 37
Message-ID: <3hsis3$nek@usenet.ucs.indiana.edu>
References: <paigenD3E73J.JGp@netcom.com> <3h76op$brp@gaia.ucs.orst.edu> <3hdp7c$1p9@awfulhak.demon.co.uk>
Reply-To: pi@nickel.ucs.indiana.edu
NNTP-Posting-Host: xyplex4-1-5.ucs.indiana.edu

Thus it was recorded by the prophets, brian@awfulhak.demon.co.uk (Brian Somers) said:
>James Miller (millerj@OES.ORST.EDU) wrote:
>: Here is the answer... at&d0\13  Keeps the modem from hanging up.
>
>I set S25=100, and run pppd/slattach immediately after kermit.  When kermit
>drops DTR, pppd/slattach pick it up before the 1 sec. timeout and the
>modem ignores the transition.

Hmmm... I have a script that I wrote to first dial up via Kermit and
then start pppd.  I tried setting S25 to the max of 2.55 seconds,
and still my modem hangs up. :-(  (It's not a *real* big deal... I
wrote my own script to send a &d2 to the modem when I'm done to hang
up the modem).

>When I'm finished, killing pppd/slattach drops DTR, and after 1 second the
>modem hangs up.

Yes, I agree that would be very nice.  I've taken care of that (albeit
in a "messy" way), but my problem is this: I'd like pppd to idle out after
a little while if it's not being used.  This seems like a real pain to 
figure out how to do.  Of course, my server is kind enough to idle out 
their end after 15 minutes so us morons don't tie up all the lines. :-)
Unfortunately, when their connection ends, not only does it take
forever for my modem to hangup, but even worse, my local pppd never
exits! :-(  This means that I have essentially no way of knowing
if the modem is connected or not without waiting forever to ping a site.
As far as I can see, there are two solutions: a) find a way to time
out my own pppd in less time than the remote waits for, or b) figure
out how to tell my pppd to call it quits (my pppd under FreeBSD 1.1R
used to behave this way--I'm running 1.1.5.1R now).  Any ideas on
either?
-- 
/----------------------------------------------------------------------------\
| Raymond L. Gilbert       | "...the present rule in computing the circle's  |
| pi@indiana.edu           |  area is entirely wrong..."                     |
| IUB Dept. of Physics     |  - Bill No. 246, Indiana State Legislature, 1897|
\----------------------------------------------------------------------------/