From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Ed Vance <EdV@macrolink.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: RE: Linux-2.4.20 modem control
Date: Wed, 19 Mar 2003 17:32:22 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.53.0303191726180.808@chaos> (raw)
In-Reply-To: <11E89240C407D311958800A0C9ACF7D1A33DEE@EXCHANGE>
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...
> diff -urN -X dontdiff.txt linux-2.4.20/drivers/char/serial.c
> patched-2.4.20/drivers/char/serial.c
> --- linux-2.4.20/drivers/char/serial.c Thu Nov 28 15:53:12 2002
> +++ patched-2.4.20/drivers/char/serial.c Tue Mar 18 16:03:43 2003
> @@ -2848,6 +2848,10 @@
> tty->driver.flush_buffer(tty);
> if (tty->ldisc.flush_buffer)
> tty->ldisc.flush_buffer(tty);
> + if (tty->termios->c_cflag & HUPCL) {
> + set_current_state(TASK_INTERRUPTIBLE);
> + schedule_timeout(HZ/2); /* 0.5 sec to disconnect modem */
> + }
> tty->closing = 0;
> info->event = 0;
> info->tty = 0;
>
Cheers,
Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips).
Why is the government concerned about the lunatic fringe? Think about it.
next prev parent reply other threads:[~2003-03-19 22:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 16:51 Ed Vance
2003-03-19 17:03 ` Richard B. Johnson
2003-03-19 22:32 ` Richard B. Johnson [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-21 0:45 Ed Vance
2003-03-21 12:24 ` Richard B. Johnson
2003-03-19 23:50 Ed Vance
2003-03-20 1:18 ` Richard B. Johnson
2003-03-20 22:13 ` Richard B. Johnson
2003-03-18 0:34 Ed Vance
2003-03-17 23:07 Ed Vance
2003-03-18 0:33 ` Richard B. Johnson
2003-03-18 18:34 ` Steve Lee
2003-03-18 19:17 ` Richard B. Johnson
2003-03-18 19:34 ` Steve Lee
2003-03-18 20:03 ` Richard B. Johnson
2003-03-20 18:51 ` Krzysztof Halasa
2003-03-17 20:07 Ed Vance
2003-03-17 21:33 ` Richard B. Johnson
2003-03-17 16:19 Richard B. Johnson
2003-03-17 19:56 ` Jamie Lokier
2003-03-17 21:12 ` Richard B. Johnson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.53.0303191726180.808@chaos \
--to=root@chaos.analogic.com \
--cc=EdV@macrolink.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®