comparison lib-src/movemail.c @ 12572:80bf29e6e978

Comment change.
author Richard M. Stallman <rms@gnu.org>
date Tue, 18 Jul 1995 00:05:14 +0000
parents 981986d7d82f
children 96819e0ab508
comparison
equal deleted inserted replaced
12571:c960e63751ec 12572:80bf29e6e978
195 if (access (inname, R_OK | W_OK) != 0) 195 if (access (inname, R_OK | W_OK) != 0)
196 pfatal_with_name (inname); 196 pfatal_with_name (inname);
197 197
198 #ifndef MAIL_USE_MMDF 198 #ifndef MAIL_USE_MMDF
199 #ifndef MAIL_USE_SYSTEM_LOCK 199 #ifndef MAIL_USE_SYSTEM_LOCK
200 /* Use a lock file named /usr/spool/mail/$USER.lock: 200 /* Use a lock file named after our first argument with .lock appended:
201 If it exists, the mail file is locked. */ 201 If it exists, the mail file is locked. */
202 /* Note: this locking mechanism is *required* by the mailer 202 /* Note: this locking mechanism is *required* by the mailer
203 (on systems which use it) to prevent loss of mail. 203 (on systems which use it) to prevent loss of mail.
204 204
205 On systems that use a lock file, extracting the mail without locking 205 On systems that use a lock file, extracting the mail without locking
206 WILL occasionally cause loss of mail due to timing errors! 206 WILL occasionally cause loss of mail due to timing errors!
207 207
208 So, if creation of the lock file fails 208 So, if creation of the lock file fails
209 due to access permission on /usr/spool/mail, 209 due to access permission on the mail spool directory,
210 you simply MUST change the permission 210 you simply MUST change the permission
211 and/or make movemail a setgid program 211 and/or make movemail a setgid program
212 so it can create lock files properly. 212 so it can create lock files properly.
213 213
214 You might also wish to verify that your system is one 214 You might also wish to verify that your system is one