RE: Linux-2.4.20 modem control

[Ed Vance <EdV@macrolink.com>]

On Wed, Mar 19, 2003 2:32 PM, Richard B. Johnson wrote:
> On Wed, 19 Mar 2003, Ed Vance wrote:
> [SNIPPED...]
> 
> > Hi Richard,
> >
> > The following patch to serial.c in 2.4.20 is a brute-force addition
> > of a hang-up delay of 0.5 sec just before close returns to the user,
> > if the hupcl flag is set. Please try this to determine if there are
> > any other issues with the remote login. If it works, I'll write a
> > better patch that does not duplicate other delays, etc.
> >
> > Cheers,
> > Ed
> >
> 
> Well, it's the "right church, but wrong pew". As soon as anything
> closes STDIO_FILENO, **bang** the modem hangs up. NotGood(tm)!
> So as long as I just execute the shell which was exec'ed ...
> getty...rlogin...bash never called close. However, `ls` on my
> machine is `color-ls` when it calls exit(0)... well you get
> the idea! I can log in, but can't actually execute anything that
> terminates, closing STDIO_FILENO...
> 
> 
Hi Richard,

Bummer! Do you think that each of those events was a "last close" 
of the port? Doesn't bash hold the port open while the `color-ls` 
runs? 

Since the path only delays (doesn't change modem control), these 
closes must have been hidden by quick reopens. Does the unmodified 
agetty set the baud rate to zero to hangup, or was that your change? 
I was thinking that I could move the delay to the code that 
disconnects when baud rate zero is set. 

your thoughts?

Cheers,
Ed

---------------------------------------------------------------- 
Ed Vance              edv (at) macrolink (dot) com
Macrolink, Inc.       1500 N. Kellogg Dr  Anaheim, CA  92807
----------------------------------------------------------------