Hi, and thanks for the reply. >> That "idiom" is a POSIX thing, we don't support it, >> and we know that we don't support it.
That was sort of my hunch. Is there a documented list of which POSIX-y things aren't supported? (E.g. in earlier implementations of PVFS, there were things missing (such as the setgid bit on directories) which work now.) If we had a "supported in POSIX, but not by PVFS2" list, we'd at least know whether things such as what we discovered today are bugs or documented features. (Just an "RTFM" is fine, if you can point me to which section of which FM to look at.) >> To support this idiom we would have to track open >> files on servers, which would mean that we'd have >> to keep shared state in the system Yeah, I understand that it would add complexity. Yet NFS manages to get this right. Is this done by some clever client-side wizardry, since NFS is a stateless protocol? Hmm ... Anyway, now that we know that read-after-unlink won't do the POSIX-compliant thing, we'll tell people not to use perl on PVFS2-resident files. (Personally, I'd prefer that nobody ever used perl for anything; but that a whole different rant ... ;-) _______________________________________________ Pvfs2-users mailing list [email protected] http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
