Re: args to fchmod() and chmod()

[Terrence Enger]

At 11:10 2003-01-20 -0500, you wrote:
>Terrence Enger writes:
>> [snip]
>
>Are you certain that it's the file type bits that are causing the
>problem?  If so, I'd say that OS/400 is definitely *incorrect*.  The

When I tried fchmod() with each single bit set in the new mode, OS/400
returned an error for each value except S_IXOTH, S_IWOTH, S_IROTH, S_IXGRP,
S_IWGRP, S_IRGRP, S_IXUSR, S_IWUSR, S_IRUSR, S_ISGID, S_ISUID.  The file
type bits came to my attention first because they caused a failure during
sanity.sh.
>above-referenced specification says that chmod sets the SUID, SGID,
>sticky, and permission bits of the file to the "corresponding bits" in
>the argument.  There is no requirement that non-corresponding bits of
>the argument be set to any particular values.

Over the last several days, I have managed to read the specification both
ways.  (If I *really* cared, I suppose I would have to spend the ink to
print that page out <grin>.)

> [snip]

>
>As per the above spec, the valid bits are precisely:
>
>       (S_ISUID | S_ISGID | S_ISVTX | S_IRWXU | S_IRWXG | S_IRWXO)

Well, uh, yes.  But not all libraries define all these names.  I have
looked at all the stat.h which are readily available to me.  These are
OS/400 V5R1, Linux gcc 2.95.3, Mingw GCC 3.2, and Visual C++ 4.0; in each
case I used the default setup for compilation.  Only the Linux compiler
defines all these names.  OS/400 comes close, omitting only S_ISVTX.  The
two Windows compilers give names to the three "on" bits of octal 0700, but
have some disagreement about what the names should be.  (Sorry to seem
dense, I allowed myself to be intimidated by the many differences between
the platforms.  On cooler consideration, most of those differences do not
impact this task.)

Thank you for your help.

Terry.

>
>-Larry Jones
>
>Nobody knows how to pamper like a Mom. -- Calvin
>
>
>_______________________________________________
>Info-cvs mailing list
>address@hidden
>http://mail.gnu.org/mailman/listinfo/info-cvs
>
>