Getaddrinfo() on glibc calls getenv(), oh boy
I think I must be missing something here, but I’ll ask anyway:<p>Why don’t the OS libraries have some sort of lock around setenv/getenv, so that only one thread can be inside them at a time? I can’t see how it could deadlock. And surely no-one is so dependent on the performance of these calls that the time to lock/unlock would be problematic?