On Tue, Jul 01, 2008 at 11:04:21AM -0400, (private) HKS wrote: > Let's hear it for my attention to detail. > > Does anybody happen to have a creative workaround for > threaded applications requesting this call? I'm experimenting > with changing the call to getpwnam(), but that's out of morbid > curiosity rather than a real fix. > > November 1 can't come soon enough ;) > > -HKS >
For a creative work-around, you can lock the getpwnam() call with a mutex and release it after you copied the returned struct passwd, however if you use a library that uses getpwnam itself, you can't avoid the screwage. If you can't wait for November, why don't you backport getpwnam_r ? Gilles > On Fri, Jun 27, 2008 at 9:20 PM, Marc Espie <[EMAIL PROTECTED]> wrote: > > On Fri, Jun 27, 2008 at 05:23:54PM -0400, (private) HKS wrote: > >> Not sure if this is the right list for this question, so let me know > >> if it needs to go > >> somewhere else. > >> > >> My OpenBSD box is missing the getpwnam_r() function described in the > >> getpwent(3) > >> man page. At least, it's described at this URL: > >> http://www.openbsd.org/cgi-bin/man.cgi?query=getpwnam&apropos=0&sektion=0&manpath=OpenBSD+Current&arch=i386&format=html > > ^^^^^^^ > > > > Have a closer look at that url. ;-) > -- Gilles Chehade http://www.poolp.org/
