A fatal error occurs if ctdbd is started with non-zero priority. sched_setschedule() cannot be called with SCHED_OTHER and a non-zero priority. This was first discovered at 1.0.89 but is still there. To reproduce, just start with: chrt -r 1 /etc/init.d/ctdb start A patch will be attached.
Created attachment 5073 [details] save off and restore the scheduling priority
As ctdb no longer uses sched_setschedule(), this can be closed