On 30 Jan 2008, at 23:03, Wesley Craig wrote: > Infinite loops should be caught by the loop breaking code in the CGI.
They either get broken by the CGI, or sometimes by the browser. Again, this isn't consistent. > cosign_check_cookie() reorders the list of connections so the last > successfully used connection is first. I just reviewed the code > that does the reorder, prompted by your report. Looks correct to me! Yes - I ran through that bit too - it looks correct to me as well. > Are you using apache2 without pre-forking? The connection list > is shared across all threads and not locked: cosign only work with > preforking. The other likely culprit is that the host in question > never had two servers in the list. We're using Apache 1.3. The host definitely started off with 2 servers - I've verified that in the server logs. Somewhere along the way it loses one of them. I've got a cosign module running with lots of debugging around that section of code - hopefully I can catch it happening this time. Simon. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Cosign-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cosign-discuss
