mirror of
https://github.com/unrealircd/unrealircd.git
synced 2026-06-12 19:14:46 +02:00
Bram Matthys
5e6bcaea33
Isn't that what it was supposed to do? Well, yes and no, previously it only guaranteed that between reconnects (so the 2nd try not being before class::connfreq than the 1st try), but there were no guarantees for the first time period directly after a squit. * When a netsplit happens and [set::server-linking::autoconnect-strategy](https://www.unrealircd.org/docs/Set_block#set::server-linking) is `sequential` (which is the default) or `sequential-fallback` (which is a good value for leafs) then we now consistently wait for [class::connfreq](https://www.unrealircd.org/docs/Class_block) seconds before trying to connect to the (same or next) server. By default this is 15 seconds in the example configuration server class. The reason for this is to provide a consistent behavior. Previously we waited semi-randomly for 0 to class::connfreq seconds. The previous behavior caused the picking of 'next server to try' to be inconsistent, which especially caused issues for `sequential-fallback`. If you want quicker recovery times in case of a netsplit, simply lower the value of [class::connfreq](https://www.unrealircd.org/docs/Class_block) in your configuration file, e.g. to 5 instead of 15 seconds. Oh yeah and for connect-strategy 'parallel' things stay as is, with the wait of 0 to class::connfreq per-server, which seems fine for that. Unless you want a 'BOOM!' effect of mass reconnects instantly, in which case you can just set class::connfreq very low.