Red Hat Bugzilla – Bug 861437
RFE: logging: Rewrite syslog logging target to be async signal safe & more flexible
Last modified: 2016-04-01 13:55:38 EDT
Description of problem:
The current libvirt logging code support for outputting syslog, just uses the regular C library syslog() function. The problem is that this function is not async signal safe, mostly because of its use of the sprintf family of functions internally. Annoyingly libvirt does not even need printf support here, because it has already expanded the log message string.
Secondary problems are that syslog() only logs to a local syslog service. It might be desirable to let it log directly to a remote syslog over TCP or UDP.
The syslog protocol is very straightforward, so the use of syslog() could easily be replaced by direct sockets calls. The Perl Sys::Syslog module is a good reference for the ever so slightly varying requirements of each OS
Version-Release number of selected component (if applicable):
Dan was this ever addressed, even indirectly? I still see syslog() calls in the code...
No, we've not addressed it yet