X-Git-Url: http://git.marmaro.de/?p=mmh;a=blobdiff_plain;f=INSTALL;h=c040874a0d161a5fd28f12dcc65236a5184ee8cb;hp=63021e4fd82556a2eb3819c88c67986c4b6e4e00;hb=ec751d9bbebd843215896b299712728eed0ea76c;hpb=8e33b82f8dc64159e993ec0e039baefd3c2a23da

diff --git a/INSTALL b/INSTALL
index 63021e4..c040874 100644
--- a/INSTALL
+++ b/INSTALL
@@ -35,6 +35,15 @@ need an ANSI C compiler such as gcc.
 
 4) make install
 
+   Note that if you have [n]mh files in your install directories with
+   the same names as the files being installed, the old ones will get
+   overwritten without any warning.  The only directory that isn't
+   true for is the `etc' directory -- in that directory, the previous
+   copy of each <file> will be backed up as <file>.prev if it differs
+   from the newly-installed copy.  Watch for any diff output while
+   make is processing that directory to see if you need to merge
+   changes from *.prev files into the new versions.
+
 5) Edit the file `mts.conf' (installed in the nmh `etc' directory)
    and make any necessary changes for the mail transport interface
    you are using.
@@ -200,21 +209,39 @@ Options for configure
      to switch between KPOP and normal POP3).  See the comments inside
      config.h for details.
 
+--with-locking=LOCKTYPE    (DEFAULT is dot)
+     Specify the locking mechanism when attempting to "inc" or
+     "msgchk" a local mail spool. Valid options are "dot",
+     "fcntl", "flock", and "lockf". Of the four, dot-locking
+     requires no special kernel or filesystem support, and simply
+     creates a file called "FILE.lock" to indicate that "FILE" is
+     locked.
+
+     In order to be effective, you should contact the site
+     administrator to find out what locking mechanisms other
+     mail delivery and user programs respect. The most common
+     reason not to use dot-locking is if the mail spool directory
+     is not world- or user-writeable, and thus a lock file cannot
+     be created.
+
 --with-mts=MTS   (DEFAULT is smtp)
-     Specify the mail transport system you want to use.  The two
+     Specify the default mail transport system you want to use.  The two
      acceptable options are "smtp" (which is the default), and
-     "sendmail".
-
-     If you use "smtp", this will enable a direct SMTP (simple
-     mail transport protocol) interface in nmh.  When sending
-     mail, instead of passing the message to the mail transport
-     agent, `post' will open a socket connection to the mail
-     port on the machine specified in the `mts.conf' file
-     (default is localhost), and speak SMTP directly.
-
-     If you use "sendmail", then `post' will send messages by
-     passing forking a local copy of sendmail.  Currently it
-     will still speak SMTP with this local copy of sendmail.
+     "sendmail".  This value will be put into the mts.conf file.  You
+     may find it convenient to specify a value at configure-time,
+     however, so that each time nmh is reinstalled, the right value will
+     be there.
+
+     If you use "smtp", this will enable a direct SMTP (simple mail
+     transport protocol) interface in nmh.  When sending mail, instead
+     of passing the message to the mail transport agent, `post' will
+     open a socket connection to the mail port on the machine specified
+     in the `mts.conf' file (default is localhost), and speak SMTP
+     directly.
+
+     If you use "sendmail", then `post' will send messages by forking a
+     local copy of sendmail.  Currently it will still speak SMTP with
+     this local copy of sendmail.
 
      If you wish to use a transport agent other than sendmail, you will
      need to use a `sendmail wrapper'.