All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Stanislav Kinsbursky <skinsbursky@parallels.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: RFC: rpcbind start/stop scripts affects all nested pid namespaces
Date: Tue, 03 Jan 2012 09:58:04 -0500	[thread overview]
Message-ID: <4F03177C.1070803@RedHat.com> (raw)
In-Reply-To: <4EF86DAF.9040804@parallels.com>

Please note, the systemV init scripts are  being replaced with 
systemd scripts, at least with Fedora 16 and beyond...

See /lib/systemd/system/rpcbind.service on Fedora 16 for
the new way rpcbind is started...

steved.

On 12/26/2011 07:50 AM, Stanislav Kinsbursky wrote:
> 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.
> 

  reply	other threads:[~2012-01-03 14:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-26 12:50 RFC: rpcbind start/stop scripts affects all nested pid namespaces Stanislav Kinsbursky
2012-01-03 14:58 ` Steve Dickson [this message]
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=4F03177C.1070803@RedHat.com \
    --to=steved@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=skinsbursky@parallels.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 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.