Re: [RFC] [PATCH 00/13] Introduce task_pid api

[Nix <nix@esperi.org.uk>]

On 20 Nov 2005, Pavel Machek stated:
> Hi!
>> I also hate bloating types and making them sparse just for the hell of
>> it.  It is seriously demoralizing to do a ps and see
>> 7011827128432950176177290 staring back at you. :)
> 
> Well, doing cat /var/something/foo.pid, and seeing pid of unrelated process
> is wrong, too... especially if you try to kill it....

I'd venture to say that anything using multiple pid namespaces should be
mounting its own private /var/run subtree (and similar for other such
directories). Consider it as similar to the problem of colliding PIDs on
multiple physical hosts, or on a host and a pile of UMLs it's running:
the solution there, too, is to unshare /var/run (by not NFS-exporting it
in the latter two cases, by private mounts in the former).

(Isn't this PID namespace stuff meant for chroots anyway?)

-- 
`Y'know, London's nice at this time of year. If you like your cities
 freezing cold and full of surly gits.' --- David Damerell