[Tickets #8577] Re: vacation rule : maildrop/mailbot locks

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/8577
------------------------------------------------------------------------------
  Ticket             | 8577
  Updated By         | rsalmon at mbpgroup.com
  Summary            | vacation rule : maildrop/mailbot locks
  Queue              | Ingo
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 2. Medium
  Milestone          |
  Patch              | 1
  Owners             |
------------------------------------------------------------------------------


rsalmon at mbpgroup.com (2009-09-15 11:26) wrote:

> To not destroy the seen-database if Ingo is being updated while  
> auto-responses are active, wouldn't it make more sense to rename the  
> vacation lock file instead? I don't follow the maildrop code  
> completely, but isn't the vacation.lock created by flock only when  
> processing the current message? That wouldn't break anything if  
> upgrading Ingo on an active system.

yes, changing maildrop's file lock will prevent live/production system  
from loosing user's db history.

So I guess the path would be (or some other file name!) :

-  $this->_action[] = '  flock "vacation.lock" {';
+ $this->_action[] = '  flock "vacationdrop.lock" {';