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

2007-10-05 Thread Stephane Chazelas
On Fri, Oct 05, 2007 at 03:25:52PM -0600, Tyler Bird wrote: [...] > Hey this worked great for seeing servers connected to port 80, but it > didn't show any servers bound and listening to port 443. Sounds like a problem in your /etc/services file. > On my system I even did a telnet 192.168.0.252

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: Malformed header from script

2007-04-16 Thread Stephane Chazelas
On Mon, Apr 16, 2007 at 09:22:08AM -0400, Michael Peters wrote: > michael watson (IAH-C) wrote: > > > If I view source in IE, the very top of the web page starts: > > > > Ensembl release 43: Gallus gallus Features on Chromosome 23 > > 6042217-6042217 > > You can't see HTTP headers when doing a

Re: Fw: Re: mod_perl closes apache's stdin and/or stdout

2007-04-03 Thread Stephane Chazelas
On Mon, Apr 02, 2007 at 03:52:50PM -0700, Stas Bekman wrote: > Stephane, you are correct in your observations that original STDIN and > STDOUT filehandles are not preserved when perlio CGI mode is used. > > This is because how Perl works. Consider the following perl program, run from > the comman

Re: mod_perl closes apache's stdin and/or stdout

2007-03-29 Thread Stephane Chazelas
On Thu, Mar 29, 2007 at 11:01:57PM +0100, Stephane Chazelas wrote: [...] > COMMAND PID USER FD TYPE DEVICESIZE NODE NAME > [...] > sh 19113 www-data0r CHR 1,3 1673 /dev/null > sh 19113 www-data1w CHR 1,3 16

Re: mod_perl closes apache's stdin and/or stdout

2007-03-29 Thread Stephane Chazelas
On Thu, Mar 29, 2007 at 09:06:20PM +0100, Stephane Chazelas wrote: [...] > print STDOUT "..."; > actually did a write(16, "..."), so STDOUT was affected another > fd that 1. Tomorrow, I'll try doing a system() within perl, but > I suspect for instance system(

Re: Fw: Re: mod_perl closes apache's stdin and/or stdout

2007-03-29 Thread Stephane Chazelas
On Thu, Mar 29, 2007 at 01:59:44PM -0700, Philip M. Gollucci wrote: > Cough: http://p6m7g8.net > No issues here. [...] Thanks Philip, I would still run lsof -ac apache2 -d0,1 on that host. You may find that some of the processes have their fd 1 closed. The problem is not especially with mod_pytho

Re: mod_perl closes apache's stdin and/or stdout

2007-03-29 Thread Stephane Chazelas
On Thu, Mar 29, 2007 at 02:49:36PM -0500, Frank Wiles wrote: > On Thu, 29 Mar 2007 10:12:00 +0100 > Stephane Chazelas <[EMAIL PROTECTED]> wrote: > > > On Wed, Mar 28, 2007 at 11:46:15AM +0100, Stephane Chazelas wrote: > > > 1. Problem Description: > > &

Re: mod_perl closes apache's stdin and/or stdout

2007-03-29 Thread Stephane Chazelas
On Wed, Mar 28, 2007 at 11:46:15AM +0100, Stephane Chazelas wrote: > 1. Problem Description: > > Hiya, > > After querying a mod_perl run CGI, the corresponding apache2 > process ends up having its fd 0 and/or fd 1 closed. This then > causes some other CGIs (for

mod_perl closes apache's stdin and/or stdout

2007-03-28 Thread Stephane Chazelas
1. Problem Description: Hiya, After querying a mod_perl run CGI, the corresponding apache2 process ends up having its fd 0 and/or fd 1 closed. This then causes some other CGIs (for instance mod_python's viewvc) to fail because they are not robust enough to cope with a closed fd 0.