summaryrefslogtreecommitdiff
path: root/lib-src/movemail.c
diff options
context:
space:
mode:
authorGlenn Morris <rgm@gnu.org>2012-08-08 09:03:04 -0700
committerGlenn Morris <rgm@gnu.org>2012-08-08 09:03:04 -0700
commit7eaa9e447dc2ea18c8828a0cbd5f005556f97c16 (patch)
tree60a34de1084d27aa83b4b90cad80e12d30e4cdc1 /lib-src/movemail.c
parentb33dcadbc2bf13079309b2afbeaad6732796bd0a (diff)
downloademacs-7eaa9e447dc2ea18c8828a0cbd5f005556f97c16.tar.gz
Refill comment
Diffstat (limited to 'lib-src/movemail.c')
-rw-r--r--lib-src/movemail.c11
1 files changed, 5 insertions, 6 deletions
diff --git a/lib-src/movemail.c b/lib-src/movemail.c
index c950d06f5d2..df1c1137df5 100644
--- a/lib-src/movemail.c
+++ b/lib-src/movemail.c
@@ -290,14 +290,13 @@ main (int argc, char **argv)
On systems that use a lock file, extracting the mail without locking
WILL occasionally cause loss of mail due to timing errors!
- So, if creation of the lock file fails
- due to access permission on the mail spool directory,
- you simply MUST change the permission
- and/or make movemail a setgid program
+ So, if creation of the lock file fails due to access
+ permission on the mail spool directory, you simply MUST
+ change the permission and/or make movemail a setgid program
so it can create lock files properly.
- You might also wish to verify that your system is one
- which uses lock files for this purpose. Some systems use other methods.
+ You might also wish to verify that your system is one which
+ uses lock files for this purpose. Some systems use other methods.
If your system uses the `flock' system call for mail locking,
define MAIL_USE_SYSTEM_LOCK in config.h and recompile movemail.