Date: Tue, 10 Nov 1998 21:35:29 +0000 From: Brian Somers <brian@Awfulhak.org> To: Sheldon Hearn <axl@iafrica.com> Cc: Dmitry Valdov <dv@dv.ru>, Kris Kennaway <kkennawa@physics.adelaide.edu.au>, Brian Somers <brian@FreeBSD.ORG>, current@FreeBSD.ORG Subject: Re: cvs commit: src/usr.sbin/ppp ip.c Message-ID: <199811102135.VAA17430@woof.lan.awfulhak.org> In-Reply-To: Your message of "Tue, 10 Nov 1998 11:14:37 %2B0200." <11258.910689277@axl.training.iafrica.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>
>
> 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.
A SIGTERM followed by a SIGINT will now bring ppp down immediately
irrespective of the current mode. A ``pppctl .... down\; quit all''
will also bring it down in a hurry.
> Hope this helps,
> Sheldon.
--
Brian <brian@Awfulhak.org>, <brian@FreeBSD.org>, <brian@OpenBSD.org>
<http://www.Awfulhak.org>;
Don't _EVER_ lose your sense of humour....
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199811102135.VAA17430>