From c424b9cb5b004a34e7b3a80fc3495a2731e933e7 Mon Sep 17 00:00:00 2001 From: fredrik Date: Sun, 17 Jun 2007 02:47:45 +0000 Subject: [PATCH] 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 --- doc/man/doldacond.8 | 4 ---- 1 file changed, 4 deletions(-) diff --git a/doc/man/doldacond.8 b/doc/man/doldacond.8 index c583f2f..b653284 100644 --- 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 .SH SEE ALSO -- 2.11.0