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
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.
"