On Sat, 31 May 2003, Michael Harrington wrote: > > How about creating a temporary file called <filename>.tab.lock to designate > that the file is being read/modified, and once done, it removes the .lock > file. Before reading the file and/or making modifications you can check for > the existence of the lock file and choose what you want to do from there. > Provides basically the same functionality you're looking for, just takes a > little bit more work, and works with the cfgfileget/cfgfileset commands. > I'm sure if someone wanted to work on it, XMail could probably use a full > "FTP-Like" protocol within the CTRL admin that supports resumes, directory > creation, binary transfers, and transaction handling on it's configuration > files, etc. But for simplicity, cfgfileget/set work fine in my opinion > (although the ability to manage directories would be nice hehe).
Ok, let's go through all those feature requests. BTW, my queue for 1.16 is already overflowing. The problem exist and this solution might have races. I'll try to find a solution because this race can happen not only with filters but with each file modified with cfgfileset/get. A locking command might work for this. - Davide - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
