From owner-freebsd-current Tue Nov 10 08:42:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13930 for freebsd-current-outgoing; Tue, 10 Nov 1998 08:42:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA13321; Tue, 10 Nov 1998 08:40:55 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id LAA06629; Tue, 10 Nov 1998 11:39:48 -0500 (EST) Date: Tue, 10 Nov 1998 11:39:48 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Sheldon Hearn cc: Dmitry Valdov , Kris Kennaway , Brian Somers , current@FreeBSD.ORG Subject: Re: cvs commit: src/usr.sbin/ppp ip.c In-Reply-To: <11258.910689277@axl.training.iafrica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10 Nov 1998, Sheldon Hearn wrote: > > > On Tue, 10 Nov 1998 11:52:33 +0300, Dmitry Valdov wrote: > > > Thanks, will be know. But why not to fix it in ppp? :) > > Hi Dmitry, > > Even if ppp does the route cleanup for you, a signal 9 (KILL) doesn't Duh. > allow it to attempt graceful exit. This means that building cleanup code > into ppp would not "fix it in ppp", since the code would never be > reached once a SIGKILL is received. > > Assuming you _want_ to send ppp a SIGKILL instead of SIGTERM, your best > bet is to run ppp from a shell wrapper script and put the route cleanup > in the script, after the line that runs ppp. > > It would be nicer, though, if you could send ppp a SIGTERM instead. I > remember that this wasn't always feasible last year when I used to use > ppp (sometimes SIGTERM would have no apparent effect), but it's worth I've noticed this too, sometimes having to SIGKILL ppp because SIGTERM didn't seem to do much of anything. > checking to see whether the software doesn't respond to this signal if > you haven't checked already. > > Hope this helps, > Sheldon. > Brian Feldman > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message