One thing we really miss in our debugging environment is lsof. The code doesn't understand AFS, so it gets confused by file descriptors on AFS files: ksh 888 wpm cwd ... node at 0xfc71eb60: can't read inode: 0 We have been talking with the current lsof author, Vic Abell <[EMAIL PROTECTED]>, who is interested in adding the necessary functionality to lsof, but has no regular access to system with AFS. Being a big paranoid Investment Bank, there is no way Morgan Stanley can provide this kind of regular access. Is there anyone in the academic or research community who might be able to help Vic out? We would all benefit from a very useful enhancement to a significant debugging tool, lsof. If you are an AFS site, and are politically and technically able to provide Vis with access, please send us and him email. We will be very grateful, and you will have the honor of getting an early alpha version of the AFS-enabled lsof ;-) Phil
