Anyway, all this started from an attempt to access env. vars from legacy
scripts running under registry. What is the easiest way to get env. var
access without the accompanying performance penalty that mod_perl
documentation talks about?
If you need to have your scripts run unmodified, have
I made a simple mod_perl change to the config and when restarting Apache
I got this error:
(98)Address already in use: make_sock: could not bind to address
0.0.0.0:2250
no listening sockets available, shutting down
/usr/local/apache/bin/apachectl: line 87: 16512 Segmentation fault
$HTTPD
I made a simple mod_perl change to the config and when restarting Apache
I got this error:
(98)Address already in use: make_sock: could not bind to address
0.0.0.0:2250
no listening sockets available, shutting down
/usr/local/apache/bin/apachectl: line 87: 16512 Segmentation fault
Hi there,
On Thu, 3 Jul 2003, Dennis Stout wrote:
I made a simple mod_perl change to the config and when restarting Apache
I got this error:
(98)Address already in use: make_sock: could not bind to address
0.0.0.0:2250
no listening sockets available, shutting down
Ged Haywood wrote:
Hi there,
On Thu, 3 Jul 2003, Dennis Stout wrote:
I made a simple mod_perl change to the config and when restarting Apache
I got this error:
(98)Address already in use: make_sock: could not bind to address
0.0.0.0:2250
no listening sockets available, shutting down
-Original Message-
From: Ranga Nathan [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 03, 2003 1:51 PM
Cc: mod_perl Mailing List
Subject: Re: Apache config problem .. please help
Ged Haywood wrote:
Hi there,
On Thu, 3 Jul 2003, Dennis Stout wrote:
I made a simple mod_perl change
I know this is not of much help, but I have had situations where a badly
terminating process would prevent subsequent processes from using that
port. on windows, i never found a solution other than to reboot. on
solaris 7, i never found a solution other than to wait 8 minutes. I did
some
Hi there,
On Thu, 3 Jul 2003, Ranga Nathan wrote:
In other words there's an Apache still running
The 'top' output is :
[snip]
How can I get a list of ports being used so I can kill the processes?
As I said, there may be more wrong than just what's obvious. It looks
like the obvious
Gedanken wrote:
I know this is not of much help, but I have had situations where a badly
terminating process would prevent subsequent processes from using that
port. on windows, i never found a solution other than to reboot. on
solaris 7, i never found a solution other than to wait 8
