Hi all, We use a DNS RR to load-balance across our cosign servers - so 'weblogin' points to 2 (or more) servers.
For server maintenance, we bring up a temporary cosign server and add it to 'weblogin', enabling us to take one of the original servers down, while keeping the same number of active servers. This isn't always a smooth process and I this seems to be because the cosign filter populates its list of servers when it starts and doesn't refresh it. This means that a change to 'weblogin' in DNS has to be followed by restarting apache across all cosign-protected sites. Perhaps the filter should re-populate its connection list from DNS? I'm not overly familiar with the code, so I'm not quite sure where this re-population should occur. And, of course, there's a danger slowing things down by doing it too often. I wonder if others also see this problem and if so, how they address it? Cheers Toby Blake School of Informatics University of Edinburgh -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Cosign-discuss mailing list Cosign-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cosign-discuss
