From owner-freebsd-current Wed Nov 15 22:26:52 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA27393 for current-outgoing; Wed, 15 Nov 1995 22:26:52 -0800 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA27382 ; Wed, 15 Nov 1995 22:26:49 -0800 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id WAA27928; Wed, 15 Nov 1995 22:25:33 -0800 To: "Rodney W. Grimes" cc: nate@rocky.sri.MT.net, msmith@atrad.adelaide.edu.au, current@FreeBSD.ORG, jhs@FreeBSD.ORG Subject: Re: startslip In-reply-to: Your message of "Wed, 15 Nov 1995 19:13:33 PST." <199511160313.TAA20307@GndRsh.aac.dev.com> Date: Wed, 15 Nov 1995 22:25:33 -0800 Message-ID: <27926.816503133@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG Precedence: bulk > Yea, what is the setup of your /dev/cuaa1 device like, I suspect that as > soon as chat closes /dev/cuaa1 it hangs up the modem. What is hupcl on > /dev/cuaa1 set to?? It shouldn't matter? The whole advantage of running chat under slattach is that it's supposed to be run on the fd that slattach already has open, so there's no question of the hangup-after-dial problem that would otherwise occur if you did the open-dial-close-slattach cycle. I know, I've been there too with my little kermit dialer scripts. Of course, if it turns out that you're right about this then slattach is deeply broken and has managed to nullify the whole advantage that was the point of adding the external dial agent capability to slattach! Jordan