Add support for logging server warning/error messages.

We can use sudo_warn_set_conversation() to set a conversation
function that either writes to a log file or calls syslog().

1 files changed, 7 insertions, 0 deletions

diff --git a/examples/sudo_logsrvd.conf b/examples/sudo_logsrvd.conf
index e73cd9998..2d42a6ab9 100644
--- a/examples/sudo_logsrvd.conf
+++ b/examples/sudo_logsrvd.conf
@@ -24,6 +24,9 @@
 # The file containing the ID of the running sudo_logsrvd process.
 #pid_file = /var/run/sudo/sudo_logsrvd.pid
 
+# Where to log server warnings: none, stderr, syslog, or a path name.
+#server_log = syslog
+
 # If true, enable the SO_KEEPALIVE socket option on client connections.
 #tcp_keepalive = true
 
@@ -219,6 +222,10 @@
 # client.
 #alert_priority = alert
 
+# The syslog facility to use for server warning messages.
+# Defaults to daemon.
+#server_facility = daemon
+
 [logfile]
 # The path to the file-based event log.
 # This path must be fully-qualified and start with a '/' character.