[Mono-dev] [PATCH] Make mod_mono restart mod-mono-server
g.moskov at gmail.com
Tue May 30 08:30:39 EDT 2006
On the other hand, this is a solution to the memory fragmentation
problems. You can set a MonoMaxMemory limit and be sure that after the
mod-mono-server is killed, it will be spawned again.
On 5/30/06, Joshua Tauberer <tauberer at for.net> wrote:
> Kornél Pál wrote:
> > When mono crashes for example because of a missing assembly
> > mod-mono-server will not be restarted automatically that causes Service
> > Unavailable error pages.
> > The attached patch restarts mod-mono-server if the socket cannot be opened.
> > This solution may not be the best but I think there is a need for
> > something like this.
> I agree.
> IIRC, the reason we don't do that now is that if you have a lot of
> incoming requests and mod-mono-server takes some time to start, you'll
> get a lot of forked mono processes -- from each request until one
> mod-mono-server gets to the point of accepting connections.
> Ideally what would be good would be to have some form of flag visible
> across the apache child processes to ensure that only one m-m-s gets
> started when it is not running -- possibly a file with a timestamp of
> the last start attempt, or something.
> - Joshua Tauberer
> "Unfortunately, we're having this discussion. It's too bad,
> because guess who listens to the discussion: the enemy."
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
More information about the Mono-devel-list