Re: Avoiding competing process (was Re: indexes)

From: Randall S. Winchester <>
Date: Wed, 7 Oct 1998 17:39:33 -0400 (EDT)
Message-ID: <>

On Wed, 7 Oct 1998, Byron C. Darrah wrote:

: > : The latest version I'm cleaning up now has locking in it to avoid
: > : the timing problems associated with very busy lists.
: Definitely cool. However, one thing users should beware of is that file
: locking doesn't work all that great over NFS. Even sendmail and pine users
: are cautioned about using an NFS directory for the mail spool because
: locking is not guranteed to work. I have found that having hypermail
: archives processed by a seperate computer (along with other jobs that do
: various web site updates) using NFS for access to hypermail files is very
: useful because it puts less load on the web server.

We use AFS alot ourselves. Locking is very much a special issue with any remote filesystem. This is one of the advantages of Hypermail (you have source). Once local system locking is in place, network locking can be considered.

Another way to also help the loading on a Hypermail server is to send all list delivery traffic to other machines for processing. You can trim both ends so the box only does hypermail tasks. But I would explore a faster bigger box along the way...

Randall Received on Wed 07 Oct 1998 11:42:08 PM GMT

This archive was generated by hypermail 2.3.0 : Sat 13 Mar 2010 03:46:11 AM GMT GMT