Rudy Gevaert wrote:
I'll try to upgrade from 2.3.7, that is our production version, to
2.3.10 on my test machine. Together with replication.
Just to confirm. I didn't see any problems (yet).
Rudy
--
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Rudy Gevaert
This would seem to be a significant advantage of running sync_client
outside master.
When I shut down master, sync_client continues to process the outstanding
log. I can then use sync_shutdown_file when it has finished and is idle.
We do something similar.
But it means you have to develop
Ken Murchison wrote:
I just put together a second release candidate for Cyrus 2.3.10 which
hopefully fixes a couple of build issues with RC1. I'd
appreciate any independent testing before I release this to the masses.
If there are any outstanding issues that you believe still need to be
On Wed, 10 Oct 2007, Rob Mueller wrote:
I think the problem at the moment is that the process you really want is:
1. Stop new imap/pop/lmtp/sieve/etc connections
2. Finish and close existing connections cleanly but as quickly as possible
3. Finish running any sync log files
4. Fully shutdown
On Fri, 12 Oct 2007, Bron Gondwana wrote:
[Bron: for some reason when you send a message to me and copy cyrus-devel,
I only see the copy sent to cyrus-devel. This doesn't happen with
messages from Rob or other members of the list, so I think that it is
something specific to your set up.
On Fri, Oct 12, 2007 at 10:29:53AM -0400, Carson Gaspar wrote:
David Carter wrote:
I'm still a little bothered about signal handling and EINTR. I did some
experiments after our last chat about signals. In practice disk IO system
calls seem to be reasonably safe against EINTR on both Linux
Or is the problem that you have something like:
write to file 1
write to file 2
And if the first returns EINTR but is ignored, and then it writes the
complete data to the second, things are in an inconsistent state?
This is my concern.
Doing an ack 'write\(' reveals a scary mix of write,
