On Tuesday 08 July 2003 03:38 am, Alan DeKok wrote: > "Earl C. Ruby III" <[EMAIL PROTECTED]> wrote: > > What is the recommended procedure for updating a shared secret with zero > > downtime? > > Source code patches to the server to allow what you tried.
Are you saying that the patches exist or are you suggesting that I should write the patches? I've considered writing the patches, but considering that I have redundant servers in two locations, I can update the shared secret at one location (client will fail over to the alternate), then have the client update their equipment (client will fail over to the updated site), then update the shared secret at the other location. I lose redundancy for one client during the switch, but if we coordinate, we should only lose redundancy for a few minutes. So this time around it's unlikely that I'll modify the server. -- Earl C. Ruby III <[EMAIL PROTECTED]> Senior Systems Engineer / Developer Switch Management - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
