- Jan 06, 2022
-
-
- Jan 05, 2022
-
-
- Jan 04, 2022
-
-
-
-
-
-
Quanah Gibson-Mount authored
-
- Jan 03, 2022
-
-
- Dec 15, 2021
-
-
-
-
-
-
-
-
A refresh can jump across multiple threads, we cannot just lock a mutex, we need to track who that is and clear when finished. In addition to that, fix our internal syncrepl session tracking pulling it closer to RFC 4533, refreshDone now represents the receipt of refreshDone flag. Refreshing status is maintained for plain refreshes (and times when we might be starting one but don't know for sure). We still reschedule a new sync with a delay if there is another one running but tracking refreshes this way paves the way to being able to wake them up if we start tracking them somehow.
-
- Dec 14, 2021
-
-
-
-
-
-
-
And have it update the listening socket names as the port gets assigned.
-
-
-
- Dec 13, 2021
-
-
- Dec 10, 2021
-
-
- Dec 09, 2021
-
-
-
We're using MANAGE_DSAIT control so we get to see them, but they don't really exist (except for their CSN sometimes).
-
-
-
Howard Chu authored
-
Howard Chu authored
-
- Dec 08, 2021
-
-