diff options
| author | bwarsaw | 2000-11-01 02:37:14 +0000 |
|---|---|---|
| committer | bwarsaw | 2000-11-01 02:37:14 +0000 |
| commit | ede1df321ca54ff96aaf2983f82e69430d720165 (patch) | |
| tree | 69151ab01cecef936f4e806c29ba9ef91c632146 | |
| parent | e3ee3db3782f87ca59e5e97d328763e1163ecc93 (diff) | |
| download | mailman-ede1df321ca54ff96aaf2983f82e69430d720165.tar.gz mailman-ede1df321ca54ff96aaf2983f82e69430d720165.tar.zst mailman-ede1df321ca54ff96aaf2983f82e69430d720165.zip | |
| -rw-r--r-- | FAQ | 8 |
1 files changed, 8 insertions, 0 deletions
@@ -51,6 +51,14 @@ FREQUENTLY ASKED QUESTIONS some cases might hang the CGI completely. In that case, switch to Apache. + It is also possible that you have stale locks. Mailman tries to + be very careful about the lock files it creates to ensure the + integrity of it's databases, but sometimes system faults can + cause stale locks to persist. Look in $prefix/locks for any + stale list locks and remove them (you can determine if they're + stale by getting the pid from the file contents and using ps to + see if those processes are still running or not). + 4. Check ~mailman/logs/error periodically: Many of the scripts have their stderr logged to |
