Linux PPP protocol development
 help / color / mirror / Atom feed
From: "cyx_mail" <cyx_mail@foxmail.com>
To: linux-ppp@vger.kernel.org
Subject: issue about PIDs ?
Date: Wed, 21 May 2008 13:31:20 +0000	[thread overview]
Message-ID: <200805212131204066521@foxmail.com> (raw)

Hi,all!                                     

	I got some kill PID issue. I think the data struct "ClientSessionStruct" connecting pppoe-server process and pppd process. So , when the server get a PADT, it can kill the child pppd process by according to the ClientSessionStruct's member pid.
	my problem:
	I modified the pppoe-server code ,and let pppoe-server spawn a pppd. then let the server send SIGTEM to pppd(using kill(pppd 2's pid , SIGTEM)) not using the normal way(such as stopsession as the code written). the pppoe-server and pppd die both, why?

	

2008-05-21 




             reply	other threads:[~2008-05-21 13:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-21 13:31 cyx_mail [this message]
2008-05-21 23:12 ` issue about PIDs ? James Cameron
2008-05-22  1:27 ` cyx_mail
2008-05-22  1:29 ` James Cameron
2008-05-22  1:37 ` cyx_mail
2008-05-22  2:37 ` James Cameron

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200805212131204066521@foxmail.com \
    --to=cyx_mail@foxmail.com \
    --cc=linux-ppp@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox