* RFC: rpcbind start/stop scripts affects all nested pid namespaces
@ 2011-12-26 12:50 Stanislav Kinsbursky
2012-01-03 14:58 ` Steve Dickson
0 siblings, 1 reply; 3+ messages in thread
From: Stanislav Kinsbursky @ 2011-12-26 12:50 UTC (permalink / raw)
To: linux-nfs@vger.kernel.org
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: RFC: rpcbind start/stop scripts affects all nested pid namespaces
2011-12-26 12:50 RFC: rpcbind start/stop scripts affects all nested pid namespaces Stanislav Kinsbursky
@ 2012-01-03 14:58 ` Steve Dickson
2012-01-10 10:39 ` Stanislav Kinsbursky
0 siblings, 1 reply; 3+ messages in thread
From: Steve Dickson @ 2012-01-03 14:58 UTC (permalink / raw)
To: Stanislav Kinsbursky; +Cc: linux-nfs@vger.kernel.org
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.
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: RFC: rpcbind start/stop scripts affects all nested pid namespaces
2012-01-03 14:58 ` Steve Dickson
@ 2012-01-10 10:39 ` Stanislav Kinsbursky
0 siblings, 0 replies; 3+ messages in thread
From: Stanislav Kinsbursky @ 2012-01-10 10:39 UTC (permalink / raw)
To: Steve Dickson; +Cc: linux-nfs@vger.kernel.org
Thanks for notice, Steve.
Will take it into account.
03.01.2012 18:58, Steve Dickson пишет:
> 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.
>>
--
Best regards,
Stanislav Kinsbursky
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-01-10 10:39 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-12-26 12:50 RFC: rpcbind start/stop scripts affects all nested pid namespaces Stanislav Kinsbursky
2012-01-03 14:58 ` Steve Dickson
2012-01-10 10:39 ` Stanislav Kinsbursky
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 NNTP newsgroup(s).