On 11/15/2011 10:09 AM, Eric Blake wrote: > Still debatable. POSIX explicitly states that the condition of errno > after a successful call to a standardized function is unspecified; that > is, a successful geteuid() may pollute errno, but it's okay, because the > user shouldn't be inspecting errno after geteuid(). > > It might be worth proposing a change to POSIX to require that geteuid() > and friends leave errno unchanged on success (in order to allow for the > GNU extension of setting errno on failure, even though POSIX did not > reserve a specific value for failure); I'll pursue that course.
Done: http://austingroupbugs.net/view.php?id=511 -- Eric Blake ebl...@redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
