[dovecot-cvs] dovecot dovecot-example.conf,1.16,1.17

[cras at procontrol.fi]

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

Modified Files:
	dovecot-example.conf 
Log Message:
Added mbox lock settings to config file. Support timeouting fcntl() and
flock() locks. Plus before the fcntl/flocks weren't even set.



Index: dovecot-example.conf
===================================================================
RCS file: /home/cvs/dovecot/dovecot-example.conf,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -d -r1.16 -r1.17
--- dovecot-example.conf	17 Nov 2002 09:42:07 -0000	1.16
+++ dovecot-example.conf	21 Nov 2002 20:13:32 -0000	1.17
@@ -177,6 +177,26 @@
 # down things as extra stat() needs to be called for each file.
 #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
+
+# 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
+# by multiple processes, but it's needed for reliable reading if no other
+# locking methods are available.
+#mbox_read_dotlock = no
+
+# Maximum time in seconds to wait for lock (all of them) before aborting.
+#mbox_lock_timeout = 300
+
+# If dotlock exists but the mailbox isn't modified in any way, override the
+# lock file after this many seconds.
+#mbox_dotlock_change_timeout = 30
+
 # If main index file is incompatible with us, should we overwrite it or
 # create a new index with another name. Unless you are running Dovecot in
 # multiple computers with different architectures accessing the same