>
> This doesn't seem to be the offending process; it's the open
> demonstrating the symptom, but much more important is the process that
> is holding the lock that it can't get.
>
> lsof on the file that it is attempting to lock ("print filename" from
> gdb) will show what process is actually holding the lock.Just to get this correct this is a problem not seen at CMU ? -- Simon
