RFC: rpcbind start/stop scripts affects all nested pid namespaces

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.

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.

Quoted 5 lines · Stanislav Kinsbursky

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.