> > On Oct 12, 2007, at 4:03 PM, Phil Carns wrote: > >> This patch is not a bug fix. I doubt that anyone wants this >> behavior, but I am sharing the patch just in case. It causes PVFS >> to _not_ report an error if a user attempts to set unsupported >> sticky or setuid bits on a file or directory. It is mainly helpful >> if you have a 3rd party application that insists on setting those >> bits and you don't want PVFS to complain about it. > > Yeah, weird usage. Does this app fail on error from the setuid, but > already has the proper permissions? > > -sam
Yeah, it is a weird case. The app checks the return code from chmod (so it fails), but in practice neither the user nor the app really needed the permission bits that were being set. Unfortunately we couldn't change the app. Oddly enough, this was apparently the behavior of PVFS1. The app did not have any trouble running there as far as I know. Sorry about the noise on this patch :) -Phil _______________________________________________ Pvfs2-developers mailing list [email protected] http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
