From owner-freebsd-hackers Tue Feb 7 05:00:29 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id FAA24644 for hackers-outgoing; Tue, 7 Feb 1995 05:00:29 -0800 Received: from wcarchive.cdrom.com (wcarchive.cdrom.com [192.216.191.11]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id FAA24638 for ; Tue, 7 Feb 1995 05:00:27 -0800 Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by wcarchive.cdrom.com (8.6.8/8.6.6) with SMTP id FAA27734 for ; Tue, 7 Feb 1995 05:00:18 -0800 Received: by dg-rtp.dg.com (5.4R2.01/dg-rtp-v02) id AA14264; Tue, 7 Feb 1995 07:59:43 -0500 Received: (rivers@localhost) by ponds.UUCP (8.6.9/8.6.5) id IAA19608; Sat, 4 Feb 1995 08:53:10 -0500 Date: Sat, 4 Feb 1995 08:53:10 -0500 From: Thomas David Rivers Message-Id: <199502041353.IAA19608@ponds.UUCP> To: terry@cs.weber.edu, peter@bonkers.taronga.com Subject: Re: chat(8) improvements for SL/IP dialout. Cc: freebsd-hackers@wcarchive.cdrom.com, longyear@netcom.com, rivers@dg-rtp.dg.com Sender: hackers-owner@FreeBSD.org Precedence: bulk > > > > > Looks nifty. One point: > > > > > t.c_lflag = 0; > > > + if(command) { > > > + /* If we're going to execute a command, don't hang-up */ > > > + /* the device when we're done. */ > > > + t.c_cflag &= ~HUPCL; > > > + } > > > t.c_cc[VERASE] = t.c_cc[VKILL] = 0; > > > > Why not? Oh, for SLIP or PPP where the command just establishes a connection > > that's useful, but for a situation where you're running some conventional > > command (like, say, a dialback security mechanism) you want to retain HUPCL. > > Or you could do what everyone has done since time immemorial and open > with a sleep the device so that the chat closer is not the final closer. > > Then the problem that the patch supposedly fixes will never occur. > > > Terry Lambert > terry@cs.weber.edu Yes, I thought about that, and considered it ugly... Let me add some motivation to this (because, I could have simply used the -r and -z flags on slattach.) My internet provider charges by the minute, thus, I'd like to connect to the modem and *not* redial. (Hmmm... perhaps a flag on slattach that says "this is how to dial the first time, but don't bother redialing if Carrier Detect goes down".) So, I had planned on doing: chat -c "slattach ..." ... to start the connection, (setting the modem to disconnect after a minute of no activity). Have sendmail do its thing, then when the modem disconnects, use the slattach option to run the "shutdown-the-link" script. Thus, since the shutdown-the-link script would have to go find the sleep and kill it, I didn't like that idea. - Dave Rivers -