And this is the backtrace. <div class="gmail_quote">2011/11/13 Arnaud Versini <<a href="mailto:arnaud.versini@gmail.com">arnaud.versini@gmail.com</a>> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> I've seen it is used by using gdb on _osl_getFullQualifiedDomainName. I don't remember how but I could provide you the bt after the build. It's not directly but _osl_getFullQualifiedDomainName is used during file locking. I'm writting a patch to remove the usage of _osl_getDomainName.<div class="HOEnZb"><div class="h5"> <div class="gmail_quote">2011/11/13 Noel Grandin <<a href="mailto:noelgrandin@gmail.com" target="_blank">noelgrandin@gmail.com</a>> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Arnaud is correct, I was looking at the wrong method. But where do you see this method being used in file locking? Lionel, I've run across a lot of machines with badly configured DNS. socket.c: _osl_getDomainName is only used by socket.c: static sal_Char* _osl_getFullQualifiedDomainName (const sal_Char *pHostName) which is only used by socket.c: static oslHostAddr _osl_hostentToHostAddr (const struct hostent *he) which is used by socket.c: oslHostAddr SAL_CALL osl_psz_createHostAddrByName (const sal_Char *pszHostname) and socket.c: oslHostAddr SAL_CALL osl_createHostAddrByAddr (const oslSocketAddr pAddr) and I assume that SAL_CALL means that these are part of the public API. </blockquote></div> </div></div>-- Arnaud Versini </blockquote></div> -- Arnaud Versini