From 736760c45b10e9a593fcd81e1a230188386ca656 Mon Sep 17 00:00:00 2001
From: Andre Noll <maan@systemlinux.org>
Date: Fri, 16 Jan 2009 00:18:20 +0100
Subject: [PATCH 1/1] Loglevel adjustments.

---
 README.afs |  8 ++++----
 audiod.ggo |  4 ++--
 filter.ggo |  2 +-
 fsck.ggo   |  2 +-
 gui.ggo    | 11 +++++++----
 recv.ggo   |  2 +-
 server.ggo | 16 ++++++++--------
 7 files changed, 24 insertions(+), 21 deletions(-)

diff --git a/README.afs b/README.afs
index 9e588a6a..01d4b52e 100644
--- a/README.afs
+++ b/README.afs
@@ -225,10 +225,10 @@ songs is
 Troubles?
 ---------
 
-Use loglevel one (option -l 1 for most commands) to show debugging
-info. Almost all paraslash executables have a brief online help which
-is displayed by using the -h switch. The --detailed-help option prints
-the full help text.
+Use the debug loglevel (option -l 0 for most commands) to show
+debugging info. Almost all paraslash executables have a brief online
+help which is displayed by using the -h switch. The --detailed-help
+option prints the full help text.
 
 para_fsck tries to fix your database. Use --force (even if your name
 isn't Luke) to clean up after a crash. However, first make sure
diff --git a/audiod.ggo b/audiod.ggo
index 8f960c67..cba65d00 100644
--- a/audiod.ggo
+++ b/audiod.ggo
@@ -9,9 +9,9 @@ text "
 
 option "loglevel" l
 #~~~~~~~~~~~~~~~~~~
-"set loglevel (1-6)"
+"set loglevel (0-6)"
 int typestr="level"
-default="4"
+default="3"
 optional
 
 option "config_file" c
diff --git a/filter.ggo b/filter.ggo
index 5376a6f8..e3ac59a2 100644
--- a/filter.ggo
+++ b/filter.ggo
@@ -2,7 +2,7 @@ option "loglevel" l
 #~~~~~~~~~~~~~~~~~~
  "set loglevel (0-6)"
 int typestr="level"
-default="4"
+default="3"
 optional
 
 option "filter" f
diff --git a/fsck.ggo b/fsck.ggo
index b893705c..eb7c6275 100644
--- a/fsck.ggo
+++ b/fsck.ggo
@@ -4,7 +4,7 @@ option "loglevel" l
 "set loglevel (0-6)"
 
 	int typestr="level"
-	default="3"
+	default="2"
 	optional
 
 option "base_dir" b
diff --git a/gui.ggo b/gui.ggo
index 40a40563..a90d1b4f 100644
--- a/gui.ggo
+++ b/gui.ggo
@@ -12,10 +12,13 @@ option "config_file" c
 option "loglevel" l
 #~~~~~~~~~~~~~~~~~~
  "set loglevel (0-6)"
-
-	int typestr="level"
-	default="4"
-	optional
+int typestr="level"
+default="3"
+optional
+details="
+	See \"para_server --detailed-help\" for the discussion of
+	loglevels.
+"
 
 option "timeout" t
 #~~~~~~~~~~~~~~~~~
diff --git a/recv.ggo b/recv.ggo
index b7003b0e..2f647613 100644
--- a/recv.ggo
+++ b/recv.ggo
@@ -2,7 +2,7 @@ option "loglevel" l
 #~~~~~~~~~~~~~~~~~~
 "set loglevel (0-6)"
 int typestr="level"
-default="4"
+default="3"
 optional
 
 option "receiver" r
diff --git a/server.ggo b/server.ggo
index 6b4770a8..2a5fabc3 100644
--- a/server.ggo
+++ b/server.ggo
@@ -4,19 +4,19 @@ section "General options"
 
 option "loglevel" l
 #~~~~~~~~~~~~~~~~~~
-"set loglevel (1-6)"
+"set loglevel (0-6)"
 int typestr="level"
-default="4"
+default="3"
 optional
 details="
-	Larger values mean less verbose output. Loglevel 1 (debug) gets
-	really noisy; a value of 2 (info) produces still noisy output,
+	Larger values mean less verbose output. Loglevel 0 (debug) gets
+	really noisy; a value of 1 (info) produces still noisy output,
 	but this won't fill up the disk quicky. Messaged logged with
-	loglevel 3 (notice) indicate normal but significant events
-	while level 4 (warning) logs unexpected events that can be
+	loglevel 2 (notice) indicate normal but significant events
+	while level 3 (warning) logs unexpected events that can be
 	handled. Unhandled error conditions are logged with loglevel
-	5 (error) and crititcal errors are logged using loglevel 6
-	(crit).  Finally, loglevel 7 (emerg) is reserved for messages
+	4 (error) and crititcal errors are logged using loglevel 5
+	(crit).  Finally, loglevel 6 (emerg) is reserved for messages
 	that cause para_server to terminate immediately.
 "
 
-- 
2.39.2