trinity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tommi Rantala <tt.rantala@gmail.com>
To: Dai Xiang <xiangx.dai@intel.com>
Cc: Dave Jones <davej@codemonkey.org.uk>, trinity@vger.kernel.org
Subject: Re: test processes are not all killed
Date: Wed, 2 Aug 2017 17:57:21 +0300	[thread overview]
Message-ID: <CA+ydwtoYiyyyiBvmMOO9ELvipyTePA8E2hmeNsU=pbhymdKSrA@mail.gmail.com> (raw)
In-Reply-To: <20170802030921.mwhtygus3oambllj@linux>

2017-08-02 6:09 GMT+03:00 Dai Xiang <xiangx.dai@intel.com>:
> On Tue, Aug 01, 2017 at 11:38:23AM -0400, Dave Jones wrote:
>> On Tue, Aug 01, 2017 at 05:38:13PM +0800, Dai Xiang wrote:
>>  > Hi!
>>  > I use below cmds(with root permission) include trinity to test and find an interesting issue:
>>  >
>>  > cmd="trinity -q -q -l off -s $seed -x get_robust_list -x remap_file_pages -N 999999999"
>>  > cd /tmp
>>  > chroot --userspec nobody:nogroup / $cmd 2>&1 &
>>  > pid=$!
>>  > sleep 300s
>>  > kill -9 $pid

Hi,

"kill -9 $pid" only kills the main trinity pid, right?
So the watchdog and all the forked child processes will not get killed.

Maybe Dave knows better if the other trinity processes will kill
themselves if they get re-parented.

Perhaps you could do "killall -9 trinity" or something like that.

-Tommi

  parent reply	other threads:[~2017-08-02 14:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-01  9:38 test processes are not all killed Dai Xiang
2017-08-01 15:38 ` Dave Jones
2017-08-02  3:09   ` Dai Xiang
2017-08-02 12:37     ` Dave Jones
2017-08-03  3:17       ` Dai Xiang
2017-08-03  3:22         ` Dave Jones
2017-08-02 14:57     ` Tommi Rantala [this message]
2017-08-02 16:41       ` Dave Jones

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='CA+ydwtoYiyyyiBvmMOO9ELvipyTePA8E2hmeNsU=pbhymdKSrA@mail.gmail.com' \
    --to=tt.rantala@gmail.com \
    --cc=davej@codemonkey.org.uk \
    --cc=trinity@vger.kernel.org \
    --cc=xiangx.dai@intel.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).