[PATCH] Declare set*id with warn_unused_result

[Paul Eggert]

On 07/24/2012 08:37 AM, Florian Weimer wrote:
> The Hurd implementation allocates a new port, so it can fail as well.

That's too bad.  It certainly strengthens the argument for
adding __wur.

Is a new port added even for seteuid?  That is, would it make
sense to add __wur for some of these system calls, but not others?
I'm asking, because on GNU/Linux anyway, EAGAIN is listed as
a possible error for setuid but not for seteuid, which suggests
that it may be useful to apply __wur to setuid but not to seteuid.