Error: FATAL Failed to initialize semaphore: Function not implemented
Arran Cudbard-Bell
A.Cudbard-Bell at sussex.ac.uk
Thu Aug 2 13:32:01 CEST 2007
Hi,
Haven't built a new copy of the server for a while, as I was mostly
debugging config stuff.
When I have built a new copy of the server from CVS i've always ran it
in full foreground debugging mode which disables threads...
Which is why I don't know exactly when the commit that causes this was
done ...
In Full debugging mode radiusd -X is fine
However running in daemon mode with debugging on I get:
Thu Aug 2 12:15:22 2007 : Debug: }
Thu Aug 2 12:15:22 2007 : Debug: Initializing the thread pool...
Thu Aug 2 12:15:22 2007 : Debug: thread pool {
Thu Aug 2 12:15:22 2007 : Debug: start_servers = 5
Thu Aug 2 12:15:22 2007 : Debug: max_servers = 32
Thu Aug 2 12:15:22 2007 : Debug: min_spare_servers = 3
Thu Aug 2 12:15:22 2007 : Debug: max_spare_servers = 10
Thu Aug 2 12:15:22 2007 : Debug: max_requests_per_server = 20
Thu Aug 2 12:15:22 2007 : Debug: cleanup_delay = 5
Thu Aug 2 12:15:22 2007 : Debug: max_queue_size = 65536
Thu Aug 2 12:15:22 2007 : Debug: }
Thu Aug 2 12:15:22 2007 : Error: FATAL: Failed to initialize semaphore:
Function not implemented
At which point GDB reports that the program exited normally, and so
won't give me the backtrace of the stack.
*sigh*
According to my colleague (who has now gone off on holiday) :
"there's an issue to do with the way semaphores are implemented on OS X
(basically, you can't use "unnamed" ones -- there's a very old thread
about this in the freeradius-users list from 2004, with workarounds).
I'm guessing that there's something wrong in the "configure" for OS X,
meaning that it isn't using the right flavour of semaphore
initialisation, OR that 2.0 has a regression to the previous problem
that was fixed in 1.x"
Any chance someone could take a look at this ?
Be happy to provide any extra information required.
Thanks,
Arran
More information about the Freeradius-Devel
mailing list