Logging Framework for C (original) (raw)
ANSI C functions and macros for flexible logging to files and other destinations.
It is modeled after the Log for Java library (http://www.log4j.org), staying as close to their API as is reasonable.
Intended for use in time-space critical environments
License
GNU Library or Lesser General Public License version 2.0 (LGPLv2)
Our Free Plans just got better! | Auth0
With up to 25k MAUs and unlimited Okta connections, our Free Plan lets you focus on what you do best—building great apps.
You asked, we delivered! Auth0 is excited to expand our Free and Paid plans to include more options so you can focus on building, deploying, and scaling applications without having to worry about your security. Auth0 now, thank yourself later.
User Ratings
2.3 out of 5 stars
★★★★★
★★★★
★★★
★★
★
ease 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5
features 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5
design 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5
support 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5
User Reviews
I am new to log4c. Could someone explain how can i use log4c to write logs to a log server? Thanks on advance.
/* user of version 1.2.{0,1}, in C project on Linux */ Log4c is fine for small project that can afford having configuration files. For larger project with a lot of processes it quickly becomes a pain to maintain thoses configuration files. And on-the-fly configuration was a pain with log4c I was disappointed by: * the use of mutexes in the logging handler, causing deadlocks when calling a logging function in a signal handler. * the strange behavior when overriding a category's logger (message dupplication). * the end-of-support and the no-answer received for support requests. * the removal of log4c from some big and official Linux distribution (i.e. Fedora Core 17) I found really easier to use the Gnome Library (GLib2.0) internal logging support. Now is my life easier, happier.
log4c is out of date, try zlog! http:[[hardysimpson.github.com/zlog Read more reviews >