Liblogging offers an enhanced replacement for the syslog() call, but retains its ease of use. In a nutshell, it permits sytem administrators to direct application log output to different destinations without requiring the app developer to do any work for this. Liblogging is released under a 2-clause BSD license and as such can be used in any application.
If you dig deeper, liblogging actually has three components, which address different needs.
stdlogThis is the component of interest for most users. It offers the syslog() API replacement. Right now, it actually does more or less what syslog() did. In the future, however, it will support different log destinations, like
- systemd journal native API
- unix domain socket
This will permit an application developer to use a single, very easy to use set of function calls to talk to any logging system. The admin will be able to configure which destination to actually use.