SIGHUP Issue Revisited / Why does squid die instead of reconfig?

Unfortunately, it seems squid-1.1.10 is just as susceptible to the
problem of receiving mystery SIGHUPs as version 1.1.20 is. So.

I've been looking through the source of 1.1.20, and am wondering why it
is that squid dies at all. From what I see in the code, squid receives
a SIGHUP, sets a global flag, and assuming program flow is somewhat
sane, it should carry out the reconfigure and continue operations
normally.

Unfortunately, this isn't the case. From what I can tell in the logs,
somehow squid thinks it's in shutdown mode, versus reconfigure mode.
I'll be poking around the source, looking for an answer. Who knows,
perhaps it interprets the SIGHUP it's receiving somehow differently than
a normal SIGHUP. So far, I haven't tested so I don't know.

Any help would be greatly appreciated.

-- 
Adam W. Dace (AD332) | E-Mail:       awd@fastparts.com
Software Programmer  | Office URL:   http://www.fastparts.com/
FastParts, Inc.      | Personal URL: http://www.turing.com/awd/
"Make it idiot-proof and someone will make a better idiot."