>it can be done though.  it just requires a little trickery.  lsof can
>do most of the tricks.

otoh..."fsck /usr" will tell me the "lost inodes", which i can then
cross-reference with my list of open files to find the culprit.

silly me...

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
andrew@crossbar.com       * "information is power -- share the wealth."