Back when it was just environment variables, I could pipe /proc/PID/environ to xargs and get basically the same state. Given that things like unix domain sockets may end up in $TMPDIR, I can be left unable to do certain things.
Back when it was just environment variables, I could pipe /proc/PID/environ to xargs and get basically the same state. Given that things like unix domain sockets may end up in $TMPDIR, I can be left unable to do certain things.
nsenter --all --target $PID
or something like that?Also you can use nsenter(8) to run a command (or even a shell) under another process’s mount, pid, network, etc namespace.
It's exactly what I was looking for, and the world can now continue to improve without breaking any of my workflows :)
/proc/$PID/ns is the place to look for namespaces
> I can be left unable to do certain things
Most of what I can imagine of "certain things" falls into two categories: debugging (for which much better tools exist), or concerns that would be better served by a program providing an API of some kind rather than "go muck with state in $TMPDIR".
Also, /proc/ is (among other things) a debug interface.