Re: ModPerl::Registry and Error Documents
> -Ursprüngliche Nachricht- > Von: "Torsten Foertsch" > Gesendet: 29.09.09 10:01:26 > An: modperl@perl.apache.org > Betreff: Re: ModPerl::Registry and Error Documents > > You have asked this question already 2 times before, on 17.09.09 12:13 > and 17.09.09 11:15. The first time I have answered it. > > If my answer is not satisfying could you be so kind and explain why? Hi Torsten, hi all others, I have to apologize for sending the same question for many times. I had problems with my mailer which let me think that my posts never arrived at the mailing list. That was also the reason for registring with another account, sending the question again. Sorry for bothering. Asking again was NOT a sign of being unsatisfied with an answer. Sorry Torsten for giving you that feeling. It was just me interpreting the outcome of an error the wrong way. Shame on me. > > Und übrigens, der Text in meiner Signatur ist ernst gemeint. Ich bin > käuflich. Wer (im weitesten Sinne) nicht... ;-) Best regards Andreas
Re: ModPerl::Registry and custom error documents
> -Ursprüngliche Nachricht- > Von: "Torsten Foertsch" > Gesendet: 17.09.09 13:14:16 > An: modperl@perl.apache.org > CC: Andreas Mock > Betreff: Re: ModPerl::Registry and custom error documents > On Thu 17 Sep 2009, Andreas Mock wrote: > > How can we dynamically create own error documents without using > > the lower level mod_perl/apache api? Is there a simple way? > > How can we achieve that? > > > Then you can configure ErrorDocuments, e.g. > > ErrorDocument 404 http://huhu.com > ErrorDocument 500 "dumm gloffe" Hi Torsten, hi all, ok, this seems to be the simple case. Thank you for this answer. Is there another way to create custom ErrorDocuments based on the return value of a ModPerl::Regisry script as long as the script has not printed to stdout yet? Best regards Andreas
Re: double mod_perl initialization
Been away from my computer for several days :( Doesn't look like anyone is going to answer this. Maybe you missed some of the emails that Clinton Gormley and I were exchanging a while back. I've been using 'sudo apachectl graceful' on apache 2.2.11 and 2.2.13 with mod_perl 2.0.4 and 2.0.5 SVN for many months now and have not noticed any problems. Of course you might be using some feature or module or ??? that my site doesn't, which would cause some problems. Fancy SSL use and changing certificates were mentioned as possibilities. If you look thru the change logs for the various apache versions you can see quite a few improvements for graceful and other restarts (there was one in 2.2.12). So why not give them a chance, and if you have problems come back here and tell us? Or look into them a little and come back and tell us even more? And if graceful restart works OK for you, please send an email to say that. The elimination of superstition is an absolute good. cmac On Oct 2, 2009, at 3:38 PM, Jonathan Swartz wrote: On Oct 2, 2009, at 3:25 PM, Perrin Harkins wrote: On Fri, Oct 2, 2009 at 5:54 PM, Jonathan Swartz wrote: Ok, one more question. Disregarding graceful for the moment - is HUP completely reliable with mod_perl at this point, or is there still a reason (as there once supposedly was) to do a full server stop and start? The problem, at least in the 1.x series, was that the parent process and the perl interpreter never restart. It just re-reads the config file and runs through startup again. Right. Ok, in a *relatively modern Apache/mod_perl 2.x*, is there still a reason to do a full server stop and start? Thanks Jon
