Are gnu syslog(), openlog() and closelog() thread-safe?

c linux gnu syslog
Konoha picture Konoha · Dec 18, 2013 · Viewed 7.1k times · Source

I have been searching for some time and haven't found a definitive answer yet. The only link I found till now which sheds some light on this is here.

Answer

alvits picture alvits · Dec 18, 2013

According to the POSIX Specification syslog(), openlog() and closelog() are thread safe.

There's another thread that answers this question as well and it is dated as far back as 2009. Here's the link syslog_r for Linux?.

Related questions

Convert milliseconds to timespec for GNU port

I want to convert milliseconds into timespec structure used by GNU Linux. I have tried following code for the same. timespec GetTimeSpecValue(unsigned long milisec) { struct timespec req; //long sec = (milisecondtime /1000); time_t sec = (time_t)(milisec/1000); req->tv_…

Read More
Seeking and reading large files in a Linux C++ application

I am running into integer overflow using the standard ftell and fseek options inside of G++, but I guess I was mistaken because it seems that ftell64 and fseek64 are not available. I have been searching and many websites seem …

Read More
Invoking GCC as "cc" versus "gcc"

I am aware that on most GNU/Linux systems, GCC can be invoked by the name "cc" from the command line (as opposed to "gcc"). Is there any difference in GCC's behavior when it is invoked one way versus the …

Read More