On Fri, Nov 27, 2009 at 01:49:26PM +0100, Alan DeKok wrote:
What is a crutch for this situation? A cron job that keeps doing radmin -e 'set home_server state X Y alive'? :)
Speaking of which, this seems to have stopped working, on the 'stable' branch:
% sudo radmin -e 'show home_server list' 127.0.0.1 1812 auth alive 0 10.0.0.1 1812 auth zombie 1 10.0.0.2 1812 auth alive 0 % sudo radmin -e 'set home_server state 10.0.0.1 1812 alive' ERROR: No such home server % sudo radmin -e 'set home_server state 10.0.0.2 1812 alive' ERROR: No such home server
Ah, yes. That's a side-effect of the TCP integration. I've committed a fix.
This makes me think we should release 2.1.8 *without* the TCP work. Followed by a 2.2.0, *with* the TCP work.
That makes sense, it's an architectural change with various possible side-effects, and there is sufficient volatility already in the 2.1 branch. :) -- 2. That which causes joy or happiness.