Re: s6-envuidgid: Weird errors with GNU libc's getgrent() and endgrent()

2019-06-02 Thread Guillermo
El dom., 2 jun. 2019 a las 12:21, Brett Neumeier escribió: > > FWIW, I compiled and ran your test program; the program output concludes with: > > name: ec2user members: (errno = Invalid argument) > End of file or error (errno = Success) > errno = Success Huh. So it looks like I've got a

Re: s6-envuidgid: Weird errors with GNU libc's getgrent() and endgrent()

2019-06-02 Thread Casper Ti. Vector
On Sun, Jun 02, 2019 at 12:02:04PM -0300, Guillermo wrote: > Do you happen to build skarnet.org packages statically linked to musl > on those Void machines, or do you let them link to the distribution's > libc? On both Alpine and Void, I use the stock packages for skaware from the distros, and

Re: s6-envuidgid: Weird errors with GNU libc's getgrent() and endgrent()

2019-06-02 Thread Laurent Bercot
Short version: For recent libc releases, and at least on Gentoo, getgrent() and endgrent() seem to magically set errno to EINVAL (I think), except when errno's value is actually meaningful. > (...) End of file or error (errno = Success) errno = Invalid argument POSIX says:

Re: s6-envuidgid: Weird errors with GNU libc's getgrent() and endgrent()

2019-06-02 Thread Casper Ti. Vector
On Sat, Jun 01, 2019 at 11:55:57PM -0300, Guillermo wrote: > Sooo... thoughts? Does anyone else use a sufficiently recent version > of GNU libc and experience the same? On my machine using Void with glibc 2.29 since 20190305, I never encountered this issue. I can confirm the behaviour you