It's like a suicide ?
If you kill Apache, you kill yourself.
Probably, you can create a detached process from your script that will
be in charge of making the stuff.
Take care about OS you are running perl on to do this.
Regards
Matthieu FEREYRE a écrit :
Is it possible to restart Apache
I had a similar issue one year ago with mod_perl 2.0.0-RC4 and perl
5.6.1 (same issue with perl 5.8).
The problem was due to the use of LibXML (which is the fastest xml
parsing library I found to parse large XML files) with mod_perl and
apache in a multi-threaded environment. I also had some
Philip M. Gollucci wrote:
Its been about 6 years since I've tried anything mod_perl windows
related, but I recall that some of the startup.pl files of that time
loaded LibXML and related by default. You might have been loading it and
just not using it.
The related problem on windows is that
I had the same problem. The only way to solve it was to use the
Apache2::Reload module. By using this module, the apache that crashed is
killed and a new process is started immediately. However, this not solve
the real problem but the popup is not displayed.
Moreover, I'm using Apache 2.0.54
Foo Ji-Haw wrote:
Hello Nikolay,
You mean you didn't use the ActivePerl distribution? You do this to
avoid the OEM licensing issue?
I am using the standard ActivePerl 5.8.7, with MP2.0.1 and Apache
2.0.52. I hope this is not the cause of the problem.
Did you try to upgrade to 2.0.54 ?
I
Hi Mark,
I had the same problem as you when installed the 2.0.0-RC6.
I patched the Apache/Reload.pm (version 0.07) as follow:
1/ Changed the string ${package}::FIELDS by
${package}::APACHE_RELOAD_FIELDS (line 43, 44, 90, 92)
2/ Changed the return value of the 'handler' function to return 0
