[Opendnssec-develop] syslog_r() on platforms that have it

[Matthijs Mekking]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Seems okay to me to.

On 06/19/2012 01:21 PM, Siôn Lloyd wrote:
> On 19/06/12 11:57, Jerry Lundström wrote:
>> On Jun 19, 2012, at 12:50 , Jerry Lundström wrote:
>>> Even tho it didn't solved the problem currently on
>>> NetBSD/OpenBSD for the EnforcerNG, is anyone against having it
>>> in?
>>> 
>>> http://fisheye.opendnssec.org/changelog/opendnssec?cs=6436
>>> 
>>> In short, openlog_r()/syslog_r()/closelog_r() is thread safe 
>>> functions on platforms where the normal functions aren't thread
>>> safe. It does not mean that the normal function does not work
>>> in threaded environments but you should use the _r() ones.
>>> 
>>> If no one is against it I'd like to push it to trunk and 1.3
>>> also.
>> 
> 
> Seems okay to me, especially when the multi-threaded enforcer code
> goes in. _______________________________________________ 
> Opendnssec-develop mailing list 
> Opendnssec-develop at lists.opendnssec.org 
> https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJP4GtvAAoJEA8yVCPsQCW5vvcIAJyhmEtGNUZKvvOnwXOH/7+z
v9YxFhoRC4cz+qtUO/sc5WS2RCW7JHocwHJd+sbrjG5BApPGKp9dlrsNCcCDuNtK
TQANWrBpe2d6iKoP9ebINLCcVLfiF4BD82QNExaiSe7dSUdV1IebqHOZPgwnBeSl
DBChL4aJW2xexYco+FdL8RxfRk2+DahOq5yrxA+Qco1x/38uBZWBQ3Yiat1o/ope
wVPOo/1SXuCLK+fbMMB5u/LUaN7QRE9joRRrlzRAEE9e7ukx8pJERNC3SvAdhqow
4Jep8hoxVTo8XKsUe5rftd94RQBIiQb0UECdF/Ce4Rb+6aPsIEXcSltGX3+l/s4=
=SSpk
-----END PGP SIGNATURE-----