Hello,
it's the first time for me writing to the list, I'm trying to change the location into which the Dovecot's locks are done reserving a special temporary directory on an other partition, then adding to the dovecont.conf the line:
mail_location = maildir:~/Maildir:VOLATILEDIR=/tmp_lock/%2.256Nu/%u
so that through the VOLATILEDIR directive the locks should be written in this path. We observe though that the locks for many users are still done in the real maildir (NFS mounted filesystem) as if in some situations this instruction is not effective. Anybody knows if are there other things to change or to do or what could be the reason? (for instance to login in a specific way or doing a particular operation).
Regards, Federico
On October 26, 2017 at 4:30 PM Federico Bartolucci <federico@aruba.it> wrote:
Hello,
it's the first time for me writing to the list, I'm trying to change the location into which the Dovecot's locks are done reserving a special temporary directory on an other partition, then adding to the dovecont.conf the line:
mail_location = maildir:~/Maildir:VOLATILEDIR=/tmp_lock/%2.256Nu/%u
so that through the VOLATILEDIR directive the locks should be written in this path. We observe though that the locks for many users are still done in the real maildir (NFS mounted filesystem) as if in some situations this instruction is not effective. Anybody knows if are there other things to change or to do or what could be the reason? (for instance to login in a specific way or doing a particular operation).
Regards, Federico
Hi, VOLATILEDIR currently only affects vsize.lock and autoexpunge.lock.
Aki
On Thu, Oct 26, 2017 at 7:30 AM, Aki Tuomi <aki.tuomi@dovecot.fi> wrote:
On October 26, 2017 at 4:30 PM Federico Bartolucci <federico@aruba.it> wrote:
Hello,
it's the first time for me writing to the list, I'm trying to change the location into which the Dovecot's locks are done reserving a special temporary directory on an other partition, then adding to the dovecont.conf the line:
mail_location = maildir:~/Maildir:VOLATILEDIR=/tmp_lock/%2.256Nu/%u
so that through the VOLATILEDIR directive the locks should be written in this path. We observe though that the locks for many users are still done in the real maildir (NFS mounted filesystem) as if in some situations this instruction is not effective. Anybody knows if are there other things to change or to do or what could be the reason? (for instance to login in a specific way or doing a particular operation).
Regards, Federico
Hi, VOLATILEDIR currently only affects vsize.lock and autoexpunge.lock.
Aki
Are there plans to expand that in 2.3? Without knowing the ramifications, it'd be nice to have lastlogin use it, at least with director enabled.
On 07.01.2018 20:05, Mark Moseley wrote:
On Thu, Oct 26, 2017 at 7:30 AM, Aki Tuomi <aki.tuomi@dovecot.fi <mailto:aki.tuomi@dovecot.fi>> wrote:
> On October 26, 2017 at 4:30 PM Federico Bartolucci <federico@aruba.it <mailto:federico@aruba.it>> wrote: > > > Hello, > > it's the first time for me writing to the list, I'm trying to change the > location into which the Dovecot's locks are done reserving a special > temporary directory on an other partition, then adding to the > dovecont.conf the line: > > mail_location = maildir:~/Maildir:VOLATILEDIR=/tmp_lock/%2.256Nu/%u > > so that through the VOLATILEDIR directive the locks should be written in > this path. > We observe though that the locks for many users are still done in the > real maildir (NFS mounted filesystem) as if in some situations this > instruction is not effective. Anybody knows if are there other things to > change or to do or what could be the reason? (for instance to login in a > specific way or doing a particular operation). > > Regards, > Federico Hi, VOLATILEDIR currently only affects vsize.lock and autoexpunge.lock. AkiAre there plans to expand that in 2.3? Without knowing the ramifications, it'd be nice to have lastlogin use it, at least with director enabled.
Yes, we have plans to expand this.
Aki
participants (3)
-
Aki Tuomi
-
Federico Bartolucci
-
Mark Moseley