From 30f36f3aa69470cf73412c7b1c209a0081bf7bf7 Mon Sep 17 00:00:00 2001
From: Robert James Kaes <rjkaes@users.sourceforge.net>
Date: Thu, 21 Sep 2000 16:53:51 +0000
Subject: Added the LOG_NOTICE level.

---
 src/log.c | 4 ++--
 src/log.h | 8 +++++++-
 2 files changed, 9 insertions(+), 3 deletions(-)

diff --git a/src/log.c b/src/log.c
index 407ff80..9fe9894 100644
--- a/src/log.c
+++ b/src/log.c
@@ -1,4 +1,4 @@
-/* $Id: log.c,v 1.2 2000-09-11 23:47:52 rjkaes Exp $
+/* $Id: log.c,v 1.3 2000-09-21 16:53:51 rjkaes Exp $
  *
  * Logs the various messages which tinyproxy produces to either a log file or
  * the syslog daemon. Not much to it...
@@ -29,7 +29,7 @@ static char *syslog_level[] = {
 	"CRITICAL",
 	"ERROR",
 	"WARNING",
-	NULL,
+	"NOTICE",
 	"INFO",
 	"DEBUG"
 };
diff --git a/src/log.h b/src/log.h
index 2be42e9..2f6b00b 100644
--- a/src/log.h
+++ b/src/log.h
@@ -1,4 +1,4 @@
-/* $Id: log.h,v 1.2 2000-09-11 23:47:52 rjkaes Exp $
+/* $Id: log.h,v 1.3 2000-09-21 16:53:51 rjkaes Exp $
  *
  * See 'log.c' for a detailed description.
  *
@@ -51,6 +51,11 @@
  *		it's default port), but it's a _higher_ level situation
  *		which the admin should be aware of.
  *
+ * LOG_NOTICE	This is for a special condition. Nothing has gone wrong, but
+ *		it is more important than the common LOG_INFO level. Right
+ *		now it is used for actions like creating/destroying threads,
+ *		unauthorized access, signal handling, etc.
+ *
  * LOG_INFO	Everything else ends up here. Logging for incoming
  *		connections, denying due to filtering rules, unable to
  *		connect to remote server, etc.
@@ -66,6 +71,7 @@
 #  define LOG_CRIT    2
 #  define LOG_ERR     3
 #  define LOG_WARNING 4
+#  define LOG_NOTICE  5
 #  define LOG_INFO    6
 #  define LOG_DEBUG   7
 #endif
-- 
cgit v1.2.3