Re: daedalus is running 2.0.31

2002-02-01 Thread Greg Ames
Aaron Bannert wrote: > Switched to use a global pool, and this gets rid of the SEGVs for > me on graceful. > > Ian: you may wish to push the tag up on this file, but it's up to you. daedalus has been updated, and graceful and non-graceful restarts are working fine once again. I'll probably try

Re: daedalus is running 2.0.31

2002-02-01 Thread Ian Holsman
Aaron Bannert wrote: > On Fri, Feb 01, 2002 at 11:26:47AM -0500, Greg Ames wrote: > > >>>It looks like the scoreboard is currently being created in the pconf >>>pool, which is cleared shortly after ap_run_mpm() decides to do a graceful. >>> >>That sounds bad. >> > > Switched to use a global

Re: daedalus is running 2.0.31

2002-02-01 Thread Aaron Bannert
On Fri, Feb 01, 2002 at 11:26:47AM -0500, Greg Ames wrote: > > It looks like the scoreboard is currently being created in the pconf > > pool, which is cleared shortly after ap_run_mpm() decides to do a graceful. > > That sounds bad. Switched to use a global pool, and this gets rid of the SEG

Re: daedalus is running 2.0.31

2002-02-01 Thread Greg Ames
Aaron Bannert wrote: > > On Fri, Feb 01, 2002 at 10:20:09AM -0500, Greg Ames wrote: > > > yep. It ran for nearly 5 hours. Then the clock struck midnight, a cron job > > kicked off a graceful restart, and: > > ...all the horses turned back into mice... ;) hee, hee :) very appropriate > I ha

RE: daedalus is running 2.0.31

2002-02-01 Thread Ryan Bloom
> I have a feeling the scoreboard is getting destroyed by it's pool cleanup > routine before this routine gets called: > > (gdb) p ap_scoreboard_image->parent > $2 = (process_score *) 0x2823500c > (gdb) p i > $3 = 0 > (gdb) p ap_scoreboard_image->parent[0] > Cannot access memory at address 0x2823

Re: daedalus is running 2.0.31

2002-02-01 Thread Aaron Bannert
On Fri, Feb 01, 2002 at 10:20:09AM -0500, Greg Ames wrote: > yep. It ran for nearly 5 hours. Then the clock struck midnight, a cron job > kicked off a graceful restart, and: ...all the horses turned back into mice... ;) > [Fri Feb 01 00:00:04 2002] [notice] Apache/2.0.31 (Unix) configured -

Re: daedalus is running 2.0.31

2002-02-01 Thread Greg Ames
jean-frederic clere wrote: > > Ian Holsman wrote: > > > > Greg Ames wrote: > > > ...since Thursday, 31-Jan-2002 19:04:06 PST. > > Cool. > > Something hangs now on daedalus! yep. It ran for nearly 5 hours. Then the clock struck midnight, a cron job kicked off a graceful restart, and: [Fri Feb

Re: daedalus is running 2.0.31

2002-02-01 Thread jean-frederic clere
Ian Holsman wrote: > > Greg Ames wrote: > > ...since Thursday, 31-Jan-2002 19:04:06 PST. > Cool. Something hangs now on daedalus! > we're running it for our developers internally starting tomorrow. > > > > > Beside checking out the tag, it has the usual patch to save the input buffers > > for

Re: daedalus is running 2.0.31

2002-01-31 Thread Ian Holsman
Greg Ames wrote: > ...since Thursday, 31-Jan-2002 19:04:06 PST. Cool. we're running it for our developers internally starting tomorrow. > > Beside checking out the tag, it has the usual patch to save the input buffers > for debugging, and a quick-n-dirty hack to exit the child without killing

daedalus is running 2.0.31

2002-01-31 Thread Greg Ames
...since Thursday, 31-Jan-2002 19:04:06 PST. Beside checking out the tag, it has the usual patch to save the input buffers for debugging, and a quick-n-dirty hack to exit the child without killing the parent if accept() gets ENFILE (system out of fd's). I did have to futz with the config file