Oh, and still another issue; dentries and /proc does not seem to
live well together:
[distance] /tmp 506> ls -al /proc/self
lrwxrwxrwx 1 root root 64 Aug 6 17:29 /proc/self -> 946
[distance] /tmp 507> ls -al /proc/946/
ls: /proc/946/exe: Permission denied
ls: /proc/946/root: Permission denied
ls: /proc/946/cwd: Permission denied
total 0
dr-xr-xr-x 3 chexum users 0 Aug 6 17:29 .
dr-xr-xr-x 87 root root 0 Aug 6 14:10 ..
-r--r--r-- 1 root root 0 Aug 6 17:29 cmdline
lrwx------ 1 root root 0 Aug 6 17:29 cwd
-r-------- 1 root root 0 Aug 6 17:29 environ
lrwx------ 1 root root 0 Aug 6 17:29 exe
dr-x------ 1 root root 0 Aug 6 17:29 fd
pr--r--r-- 1 root root 0 Aug 6 17:29 maps
-rw------- 1 root root 0 Aug 6 17:29 mem
lrwx------ 1 root root 0 Aug 6 17:29 root
-r--r--r-- 1 root root 0 Aug 6 17:29 stat
-r--r--r-- 1 root root 0 Aug 6 17:29 statm
-r--r--r-- 1 root root 0 Aug 6 17:29 status
So of course, dentries are somehow not removed for pid directories.
And... I hope anon pipes/socket names will return in some form, proc/*/fd
output would be so much more informative. I'm not interested in peeking
into others unnamed pipes, but at least I'd like to know that it's a pipe
between which two processes. Same for sockets, I don't think it's justified
to be able to push data into a program's socket, but it would be nice to know
that it's a socket, and then be able to identify where the socket is connected,
etc.
Also /proc/*/maps could be made prettier to contain the filenames, but it
might be kludgy to hook into the /proc output. But maybe yes, by exploiting
the usual /proc trick to modify the file pointer to where the map starts.
-- Janos - Don't worry, my address works. I'm just bored of spam.