Nemo wrote: > When a ORCLOSE file is created by a process at > machine A into a FS at machine B, if the machine > A goes away (e.g., you power it down), the file > is not removed.
I believe this. > This is as it could be expected, because > ORCLOSE, IFAIK, is processed by the kernel during the cleanup > done for the process while it exits. But this is not true. ORCLOSE is processed by the remote server. The kernel does not handle it specially when talking to a remote 9P server. (It does handle ORCLOSE for local devices like devenv and devsrv.) I think what you are seeing is just a bug in fossil. fidClunkAll should test for (fid->open & FidORclose) and then do the remove. If you implement and test it I'd be happy to see a patch. Erik wrote: > how would the fs determine that the machine hosting the > client is in casters-up mode? Loss of the TCP or IL connection is the usual sign. Russ
