De-listed fixed bug from doldacond.8.

git-svn-id: svn+ssh://svn.dolda2000.com/srv/svn/repos/src/doldaconnect@1077 959494ce-11ee-0310-bf91-de5d638817bd

diff --git a/doc/man/doldacond.8 b/doc/man/doldacond.8
index c583f2f..b653284 100644 (file)
--- a/doc/man/doldacond.8
+++ b/doc/man/doldacond.8
@@ -135,10 +135,6 @@ attach \fBgdb\fP(1) (or your debugger of choice) to the running
 \fBdoldacond\fP process and set the hashjob variable to -1, which will
 force \fBdoldacond\fP to resume hashing. Don't do that while a hash
 job is actually running, though.
-.P
-Not really a bug in \fBdoldacond\fP itself, many PAM modules will
-reinitialize the syslog library and cause log messages from the daemon
-itself to arrive to a different facility than originally intended.
 .SH AUTHOR
 Fredrik Tolf <fredrik@dolda2000.com>
 .SH SEE ALSO