[dovecot-cvs] dovecot dovecot-example.conf,1.38,1.39

[cras at procontrol.fi]

Update of /home/cvs/dovecot
In directory danu:/tmp/cvs-serv113

Modified Files:
	dovecot-example.conf 
Log Message:
Don't use flock() locking by default. Using both fcntl+flock doesn't work
with FreeBSD.



Index: dovecot-example.conf
===================================================================
RCS file: /home/cvs/dovecot/dovecot-example.conf,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -d -r1.38 -r1.39
--- dovecot-example.conf	30 Jan 2003 17:59:31 -0000	1.38
+++ dovecot-example.conf	8 Feb 2003 13:43:13 -0000	1.39
@@ -239,12 +239,17 @@
 # specifies that existing message are immutable.
 #maildir_check_content_changes = no
 
-# Which locking methods to use for locking mbox. All of them are used by
-# default. flock is ignored in systems which don't have it. Note that the
-# order of fcntl and flock are important to prevent deadlocks if they're both
-# also used by other programs accessing the mailbox. Dotlock file is always
-# created first.
-#mbox_locks = dotlock fcntl flock
+# Which locking methods to use for locking mbox. There's three available:
+#  dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe
+#           solution. If you want to use /var/mail/ like directory, the users
+#           will need write access to that directory.
+#  fcntl  : Use this if possible. Works with NFS too if lockd is used.
+#  flock  : May not exist in all systems. Doesn't work with NFS.
+#
+# You can use both fcntl and flock too; if you do the order they're declared
+# with is important to avoid deadlocks if other MTAs/MUAs are using both fcntl
+# and flock. If dotlock is used, it's always created first.
+#mbox_locks = dotlock fcntl
 
 # Should we create dotlock file even when we want only a read-lock? Setting
 # this to yes hurts the performance when the mailbox is accessed simultaneously