>-----Original Message----- >From: Joshua Slive [mailto:[EMAIL PROTECTED] >On Tue, 25 May 2004, Mathihalli, Madhusudan wrote:
>> AIUI, the 'graceful' restart forces the child processes join all the >> threads and re-start. (Pl. let me know if this is incorrect). >> >> The requirement is to update the crl without causing the process to >> re-start in order to achieve a zero down-time. > >Yes, the "graceful" restart does force all the child >process/threads to >restart. But it does so in a "graceful" manner: workers are >not killed >until they are done serving requests and new workers are >started before >the old ones are killed in order to assure that there is >always a pool of >workers available to serve new connections. > >Theoretically, "apachectl graceful" should have zero down-time >from the client perspective. Hmmn.. I didn't realize that ! I'll check it out. I was blinded by the PID's change after a 'graceful' restart :-(. Regarding the other aspect - do people think it's worth having a re-read hook ? (With my HP hat on) I've come across a lot of customers who need the online CRL update feature. I thought of providing a OCSP interace OR a LDAP interface (to access CRL from a LDAP database) - but then they're concerned that it'll slow things down. Hence, I had to provide a re-read mechanism. If we come up with a re-read hook, it'll probably help lot many other modules also. -Madhu
