README.afs: Add some information on para_fsck.

diff --git a/README.afs b/README.afs
index dd80914495d32569fa05e997e5a3a35d1e9da824..d77f6bfa39a84fdb35304f1f55d4344d7160ba86 100644 (file)
--- a/README.afs
+++ b/README.afs
@@ -223,12 +223,33 @@ songs is
 ---------
 Troubles?
 ---------
-If something went wrong, look at the output. If that does not give
-you a clue, 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.
-
-Still not working? Mail the author Andre Noll <maan@systemlinux.org>
-(english, german, or spanish language). Please provide enough info
-such as the version of paraslash you are using and relevant parts of
-the logs.
+
+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.
+
+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
+para_server isn't running before executing para_fsck if para_fsck
+complains about busy (dirty) tables. para_fsck also contains an option
+to dump the contents of your the contents of the database to the file
+system.
+
+If you don't mind to recreate your database you can start
+from scratch by removing the entire database directory, i.e.
+
+       rm -rf ~/.paraslash/afs_database
+
+Note that this removes all tables, in particular attribute definitions
+and data, and all playlist and mood definitions.
+
+para_fsck operates on the osl-layer, i.e. it fixes inconsistencies
+in the database but doesn't know about the contents of the tables
+contained therein. Use
+
+       para_client check
+
+to print out bad entries, e.g.missing audio files or invalid mood
+definitions.
+
+Still having problems? mailto: Andre Noll <maan@systemlinux.org>