Re: [PATCH 1/2] run-command: Add checks after execvp fails with EACCES

On Wed, 14 Dec 2011 15:31:25 +0100, Frans Klaver [off-list ref]  
wrote:

Since fopen() uses the effective uid/gid, it then makes sense to use
eaccess(3) instead of access(2) if available. It would be stupid to
have bugs arise just because of a mismatch between the [ug]ids used by
the two access checks. I'm aware of the fact that eaccess isn't a
standard function, so a #define HAVE... fallback to at least access()
would probably be required.

Just to be clear, I don't really want to restart the discussion of which  
uid to use, but it is something to consider now or in the future. The next  
roll will use access(2) as far as I'm concerned.