Miguel,

I was looking through the sysklogd patch that you provided, and looked through the glibc code.  I don't see any __libc_lock magic happening.  Since ctime isn't reentrant, no effort is made to protect the coder against threaded programming.  I also checked the 'time' function in case you were worried about that.

Which glibc function were you worried about?

I can see this code being included for completeness so that an entry isn't lost, but I don't think this is what's causing your breakage.

TKs,
Jeff Bailey

Reply via email to