From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/3966 Path: main.gmane.org!not-for-mail From: "Edward J. Sabol" Newsgroups: gmane.emacs.gnus.general Subject: Re: Gnus5, procmail, and reading mail lists. Date: Tue, 14 Nov 1995 14:52:27 -0500 Message-ID: <199511141952.OAA21001@thuban.gsfc.nasa.gov> References: NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035144780 28099 80.91.224.250 (20 Oct 2002 20:13:00 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 20:13:00 +0000 (UTC) Return-Path: ding-request@ifi.uio.no Original-Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by miranova.com (8.6.11/8.6.9) with ESMTP id MAA18335 for ; Tue, 14 Nov 1995 12:46:41 -0800 Original-Received: from thuban.gsfc.nasa.gov (thuban.gsfc.nasa.gov [128.183.127.167]) by ifi.uio.no with ESMTP (8.6.11/ifi2.4) id for ; Tue, 14 Nov 1995 20:52:29 +0100 Original-Received: (from sabol@localhost) by thuban.gsfc.nasa.gov (LHEA9504/950407.s1) id OAA21001; Tue, 14 Nov 1995 14:52:27 -0500 Original-To: Ding Gnus Mailing List In-reply-to: (message from Joe Hildebrand on 13 Nov 1995 15:43:23 -0700) Xref: main.gmane.org gmane.emacs.gnus.general:3966 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:3966 Excerpts from [ding]: (13-Nov-95) Re: Gnus5, procmail, and reading mail lists. by Joe Hildebrand >> "Steven" == Steven L Baur writes: Steven> LOCKEXT=+ Steven> I thought movemail *did* use .lock for an extension. At least that's Steven> what the XEmacs sources seem to imply. >> "Joe" == Joe Hildebrand writes: Joe> I got that from somewhere.... anyone want to 'fess up? I haven't lost Joe> any mail (that I know of :) using either that or the default. Maybe I'll Joe> go have a look at the 19.29 movemail source. I don't know about 19.29, but 19.28 most definitely uses "foo.lock" semaphore files for locking, and *not* "foo+". I find it hard to believe that they would change that for 19.29. Also, in 19.28, movemail would only use "foo.lock" semaphore files if and only MAIL_USE_LOCKF and MAIL_USE_FLOCK are both undefined. Otherwise, it uses lockf() or flock() respectively. I advise everyone who has "LOCKEXT=+" in his/her .procmailrc file to check the source code for movemail and verify this. If you have procmail set to use "foo+" semaphore files and movemail only recognizes "foo.lock" semaphore files, you can and probably will lose e-mail at some point, unless you have MAIL_USE_LOCKF or MAIL_USE_FLOCK defined, in which case it's a moot point what the name of the locking semaphore file is. (Please note that you should *not* have MAIL_USE_LOCKF or MAIL_USE_FLOCK defined if your mail spool directory is NFS-mounted. If that's the case, then you should always use semaphore lock files.) Later, Ed