[Pommed-commits] r444 - trunk

[jblache at alioth.debian.org]

Author: jblache
Date: 2008-02-27 20:00:20 +0000 (Wed, 27 Feb 2008)
New Revision: 444

Modified:
   trunk/README
Log:
Add some debug information.


Modified: trunk/README
===================================================================
--- trunk/README	2008-02-27 19:52:54 UTC (rev 443)
+++ trunk/README	2008-02-27 20:00:20 UTC (rev 444)
@@ -5,6 +5,7 @@
  - Supported machines
  - Using pommed
  - Beeper feature
+ - When things go wrong
  - Using gpomme and wmpomme
 
 
@@ -94,6 +95,37 @@
 to pommed through this device, and pommed only needs to ... well, *beep*.
 
 
+When things go wrong
+--------------------
+
+First and foremost: don't panic!
+
+If something doesn't work (or so it appears), there's usually a good reason to
+that, and pommed should be able to provide some insight as to what is going
+wrong if only you ask it.
+
+By default, pommed uses syslog to log warnings and errors, so check your
+system logs. If you can't find anything, running pommed in the foreground
+will help a lot; in this mode, pommed will log everything to stderr instead
+of syslog, so you'll see every message.
+
+First, stop pommed. Then run
+ # pommed -f
+
+Use Ctrl-C to stop pommed, fix the problem, and restart it.
+
+If you still can't see what's wrong, ask for more output by running pommed in
+debug mode. Be warned: in this mode, pommed is very chatty.
+
+First, stop pommed. Then run
+ # pommed -d
+
+Use Ctrl-C to stop pommed, fix the problem, and restart it.
+
+If the debug mode doesn't offer any hint as to what's going on, then contact
+me with the details of your problem and I'll be able to help.
+
+
 Using gpomme and wmpomme
 ------------------------