bug-hurd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Non-compliant access behavior?


From: Samuel Thibault
Subject: Re: Non-compliant access behavior?
Date: Thu, 24 Dec 2009 10:48:59 +0100
User-agent: Mutt/1.5.12-2006-07-14

J de Boyne Pollard, le Wed 23 Dec 2009 12:41:30 -0800, a écrit :
> ST> Apparently access() restricts itself to the real gid, without
> ST> including supplementary group IDs.
> 
> As IEEE 1003.1:2004 says, at least by omission, it should.  There's no
> mention of supplementary group IDs in the definition of the access()
> call.

That's why I put a question mark in the subject.

The problem I encountered is that I couldn't run gcc over files in a
directory which belonged to a group my I was in.  I hope you'll too find
it quite surprising.  Be it POSIX-compliancy or not, I believe following
what gcc thinks is compliant would be useful.

Samuel




reply via email to

[Prev in Thread] Current Thread [Next in Thread]