> Think about multiple processes owned by multiple users running on a > cpu server. Which processes should be allowed to join which > namespaces? > > Perhaps allowing only the hostowner to join namespaces for debugging > and administration purposes would be acceptable.
Ah, right. What about only allowing a process to join another namespace if the user is the same? > This seems a contrived example. Would you really spend HOURS working > on setting up a namespace by hand? Surely you would instead be > working on a script that builds the namespace for you; make the > computer do the work. Then when you mess up, you can modify the > script, create a new window, and try again. Yes, good point. That's the best way to do it. Also screen file can help add commands to the script post facto. The hours term isn't so much in the development of the environment but more to do with the amount of time you could be working in that shell instance. All the while not remembering all of the things you did to the namespace and environment in that time. Cheers, Chris
