From owner-freebsd-current Tue Nov 10 01:17:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA00470 for freebsd-current-outgoing; Tue, 10 Nov 1998 01:17:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from axl.training.iafrica.com (axl.training.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA00455; Tue, 10 Nov 1998 01:17:24 -0800 (PST) (envelope-from sheldonh@axl.training.iafrica.com) Received: from sheldonh (helo=axl.training.iafrica.com) by axl.training.iafrica.com with local-esmtp (Exim 2.05 #1) id 0zd9sj-0002vb-00; Tue, 10 Nov 1998 11:14:37 +0200 From: Sheldon Hearn To: Dmitry Valdov cc: Kris Kennaway , Brian Somers , current@FreeBSD.ORG Subject: Re: cvs commit: src/usr.sbin/ppp ip.c In-reply-to: Your message of "Tue, 10 Nov 1998 11:52:33 +0300." Date: Tue, 10 Nov 1998 11:14:37 +0200 Message-ID: <11258.910689277@axl.training.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 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 checking to see whether the software doesn't respond to this signal if you haven't checked already. Hope this helps, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message