Is there a way to force the Netapp to forget about specific locks? I know how to get the Netapp to forget about *all* locks from a particular client, but I don't always want that.
My specific problem is with the FrontPage extensions on Solaris (using Apache as the web server). Once in a while, the extensions think there is another instance running. It determines this by attempting to lock a file called vti_pvt/service.lck .
I can run lock_dump on the Netapp and see the inode and client- side pid that was granted the lock, but in some cases that pid is no longer extant. All the FP documentation I've seen says "kill off the hung process", which doesn't apply here. I've been able to work around the problem each time simply by renaming/removing the service.lck file, but I thought I should at least investigate the possibility of removing entries from the Netapp's table of locks.