Re: Best version of Apache for Win32 deployment

2007-10-02 Thread William A. Rowe, Jr.
Foo JH wrote:
> Hi all,
> 
> Just want to share something I read today (fairly old news) at
> ApacheLounge:
> http://www.apachelounge.com/forum/viewtopic.php?t=1907
> 
> Since many (most?) people who use Apache from Apache Lounge also use
> mod_fcgid and/or mod_perl, it seems that 2.2.5 will remain the best
> Apache version to use until Apache 2.2.7 comes out.

Right.  Except there is no 2.2.5; you are best staying with 2.2.4 IF you
can live without 'rotatelogs' or other piped logs, AND you need mod_perl
or mod_fcgid.  If you don't use these modules you are best off using 2.2.6
which was released.

> It is expected that new versions of mod_fcgid and mod_perl will be
> needed for Apache 2.2.7, because the proposed changes will not be
> backward-compatible with Apache 2.2.5 and earlier.
> 
> My point is that for Win32 modperlers, you may want to check out 2.2.5,
> and hold out for 2.2.7 (and a potentially new release of modperl to
> support it).

Again, there is no 2.2.5, so there is no purpose to your struggling with
it and any associated bugs.  Also Tom Donovan has cautioned users against
using the hacks they applied to 2.2.6 to get it to work, use it if you
must but it's apropos of nothing to the final corrections.

Of course 2.2.4 essentially worked, while 2.2.7 will give the modperl'ers
on Windows something they have BEGGED for forever, the chance to see parsing
errors at startup from their httpd.conf file(!!!)

ALL 2.x versions of Apache on Windows had never hooked up the pseudo-posix
stderr of MSVCRT, which is why fprintf(stderr...) constructs from within
modperl rarely did what they were expected to do.  With the 2.2.6 version,
things broke further as stdin went away after it was consumed (it was replaced
with NULL, but not at the MSVCRT layer).

If you update to svn.apache.org/repos/asf/apr/apr/branches/1.2.x/ today,
you'll find the 80/20 has been resolved; we now plug into pseudo-posix
handles.  There are still some lingering issues to be fixed in httpd itself.
Tom Donovan and Randy have already approved with Win32 fixes, but we still
are waiting on an httpd'er to review the essential fix to log.c.  I'll
send another note to the modperl community when we believe that the
svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x/ is ready for intensive
review and testing, after that patch is applied (same applies to 2.0.x, needs
patch review, while apr/branches/0.9.x/ has already been patched).

Bill


Best version of Apache for Win32 deployment

2007-10-02 Thread Foo JH

Hi all,

Just want to share something I read today (fairly old news) at ApacheLounge:
http://www.apachelounge.com/forum/viewtopic.php?t=1907

Since many (most?) people who use Apache from Apache Lounge also use 
mod_fcgid and/or mod_perl, it seems that 2.2.5 will remain the best 
Apache version to use until Apache 2.2.7 comes out.


It is expected that new versions of mod_fcgid and mod_perl will be 
needed for Apache 2.2.7, because the proposed changes will not be 
backward-compatible with Apache 2.2.5 and earlier.


My point is that for Win32 modperlers, you may want to check out 2.2.5, 
and hold out for 2.2.7 (and a potentially new release of modperl to 
support it).


Re: monitoring server and which ports they are connected to.

2007-10-02 Thread Stephane Chazelas
On Tue, Oct 02, 2007 at 01:01:52PM -0700, Manoj Bist wrote:
> Try 'sudo lsof -i:443'.
[...]

See also:

ss -a 'src :https'

(ss is part of iproute, the new suite of ip managment tools for
Linux).

Cheers,
Stephane


Re: monitoring server and which ports they are connected to.

2007-10-02 Thread Manoj Bist
Try 'sudo lsof -i:443'.

This is what I get on my system.

sudo lsof -i:443
COMMAND   PID USER   FD   TYPE  DEVICE SIZE NODE NAME
apache2 14550 root5u  IPv6 2251478   TCP *:https (LISTEN)
apache2 14589 www-data5u  IPv6 2251478   TCP *:https (LISTEN)
apache2 26533 www-data5u  IPv6 2251478   TCP *:https (LISTEN)

On 10/2/07, Tyler Bird <[EMAIL PROTECTED]> wrote:
> Hi list,
>
> I am frustrated trying to restart apache and it complaining it can't
> bind to port 443 when
> it seems no services are attached to it.
>
> Does anyone know any command line utility that can report which programs
> are attached to which tcp port?
>
> any one know they correct netstat options to report this.
>
> Thanks in advance!
>
> Tyler
>


monitoring server and which ports they are connected to.

2007-10-02 Thread Tyler Bird

Hi list,

I am frustrated trying to restart apache and it complaining it can't 
bind to port 443 when

it seems no services are attached to it.

Does anyone know any command line utility that can report which programs 
are attached to which tcp port?


any one know they correct netstat options to report this.

Thanks in advance!

Tyler