> >> Another aspect I noticed is that what you seem to need is a > >> finer-grained construction of #p and #s, but being able to construct > >> them one layer further down the hierarchy might suffice. > > > > "one layer further down the hierarchy" ? > > > Well, if you could bind a subset of #s by some selection criterion - > specifically process group, but who's to know what else might be > useful? - say, back onto a local /srv, you may have a sensible > mechanism for jailing processes. But I'm once again speculating > outside my knowledge and experience.
why not just avoid /srv and #s alltogether? the jailer could do the mounts before starting the prisoner. this way, no access to #s would be required. - erik
