Fredrik Nyberg DC <nba@...> wrote: > I'm working on a prototype, I'm using 'sync' to dump the entire textfile > with proper locking. However, I'll have to think about race-conditions a > bit, since I was thinking of locking _all_ the peers for the sync to > ensure that the databases are not flushed during the update. The peer > that is out of sync would then have to have some algortihm to decide > which database from the other peers it wants (oldest entry, newest > entry, most entries, etc) since the databases are not guaranteed to be > in sync (imagine a powerout in the server-room). I'll probably need some > kind of timeout for the actual transfer, too. Yes, there is the problem of choosing the best source. Looking for latest entry sounds good. This can be done by another command to get the latest database update date. A starting machine would ask all the peers and would look its dump file, then choose the best way to reload the greylist and whitelist. -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu@...
Message
Re: [milter-greylist] mx-syncing
2005-06-10 by manu@netbsd.org
Attachments
- No local attachments were found for this message.