On 25/01/2013 23:32, Helmut Karlowski wrote:
It suffices that any active process has it's cwd there to inhibit renaming the parent-directory, which is likely the case.
By looking at /kern/*/cwd, I see that most processes with low PID have their cwd set to the XaAES directory, including fVDI. Usually, it is a good habit that resident services set their cwd to / to avoid lock troubles.
Any potential change in that area should happen after the release, though, because of eventual bad side effects.
BTW: Those /kern/*/cwd symlinks look ugly with ls -l, it would be a good idea to fix them (after the release) so they display the target directory.
I had to cd to those cwd directories to see the contents and understand where I was.
# ls -l /kern/1/cwdlrwx------ 1 root root 0 Jan 26 12:12 /kern/1/cwd -> [0002]:537880576
-- Vincent Rivière