6 Commits

Author	SHA1	Message	Date
Martin Schwenke	1a8d431936	ctdb-logging: Add logging via UDP logging using RFC5424 ... Some implementations may not understand RC3164 format messages on the UDP socket, so add support for RFC5424 message format. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>	2014-10-28 05:42:04 +01:00
Martin Schwenke	8ed3ff456c	ctdb-logging: Add logging via UDP to 127.0.0.1:514 to syslog backend ... This has most of the advantages of the old logd with none of the complexity of the extra process. There are several good syslog implementations that can listen on the UDP port. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>	2014-10-28 05:42:04 +01:00
Martin Schwenke	a6e770ec28	ctdb-logging: Add non-blocking Unix domain logging to syslog backend ... Format messages as per RFC3164. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>	2014-10-28 05:42:04 +01:00
Martin Schwenke	1d1cd04cb9	ctdb-logging: New option CTDB_LOGGING, remove CTDB_LOGFILE, CTDB_SYSLOG ... Remove --logfile and --syslog daemon options and replace with --logging. Modularise and clean up logging initialisation code. The initialisation API includes an app_name argument that is currently unused - this will be used in extensions to the syslog backend. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>	2014-10-28 05:42:04 +01:00
Martin Schwenke	2974554356	ctdb-logging: Replace logd code with a basic syslog(3) implementation ... It is much simpler for most cases to have a syslog backend that doesn't need a separate CTDB-specific logging daemon. This loses the lossy, non-blocking mode provided by logd. However, a corresponding feature with a completely different implemention (not requiring an extra daemon) will be re-added into the syslog backend. In an ideal world the new implementation would be added first but unfortunately that is hard to do because the logd code is hooked in at more than one place. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>	2014-10-28 05:42:04 +01:00
Martin Schwenke	739324eead	ctdb-logging: Separate out syslog and file logging backends ... This makes the code cleaner and allows the syslog backend to be easily modified without affecting other code. Also do some extra clean-up, including whitespace fixups. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>	2014-10-28 05:42:04 +01:00