All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislav Kinsbursky <skinsbursky@parallels.com>
To: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: RFC: rpcbind start/stop scripts affects all nested pid namespaces
Date: Mon, 26 Dec 2011 16:50:55 +0400	[thread overview]
Message-ID: <4EF86DAF.9040804@parallels.com> (raw)

When trying to start and stop rpcbind in different pid namespaces I've noticed, 
that rpcbind stop command kills all rpcbind processes in nested pid namespaces.
This is caused by "/sbin/pidof rpcbind" call on rpcbind start. IOW file 
"/var/run/rpcbind.pid" contains pids of all nested rpcbind processes.
The simplest solution I see for now is to add "-c" options to "pidof" command. 
But I'm not sure about quality of solution and probably "killall5" have to be 
updated with new option to work only in current pid namespace.
Would be glad to hear any opinion about this problem.

-- 
Best regards,
Stanislav Kinsbursky

             reply	other threads:[~2011-12-26 12:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-26 12:50 Stanislav Kinsbursky [this message]
2012-01-03 14:58 ` RFC: rpcbind start/stop scripts affects all nested pid namespaces Steve Dickson
2012-01-10 10:39   ` Stanislav Kinsbursky

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=4EF86DAF.9040804@parallels.com \
    --to=skinsbursky@parallels.com \
    --cc=linux-nfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.