[general-l] -ERR: received signal #13 {02}

[Miguel A. Argañaraz² ®]

I think is a Bug, because I only get this error in only one case.

What I have different from each network/configuration is that this special
case has a Firewall-1 as a firewall. When he tries to connect
I see "-ERR: received signal #13" in the log, and the connection is refused.

I have tried the ftp.proxy with an public ip address in the client host,
and trought a linux doing masquerading, using an active ftp session, and 
everything
works flawlesly.

What else do you need in order me to help you?

Regards,
Miguel.


----- Original Message ----- 
From: "BARBIER GREGOIRE" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, December 10, 2002 2:14 PM
Subject: RE: [general-l] -ERR: received signal #13 {01}


> De : Miguel A. Argaqaraz2 . [EMAIL PROTECTED]
> > Hi,
> > 
> > When I try to connect to my static ftp server through the ftp.proxy
> > I got signal #13 error, could you tell me what is that? Not always
> > happend this but with certaing host client.
> > 
> > ftp.proxy[12058]: connected to client: host.domain.com
> > ftp.proxy[12058]: info: monitor mode: on, ccp: <unset>
> > ftp.proxy[12058]: -ERR: received signal #13
> > 
> > inetd.conf:
> > 
> > ftp     stream  tcp     nowait  root    /usr/sbin/tcpd 
> > /usr/local/sbin/ftp.proxy -m 192.168.0.1
> > 
> > What can I do in order to fix this?
> > Thanks in advance.
> > 
> > --
> > Regards,
> >         Miguel.
> 
> Signal #13 (SIGPIPE) is send to processes that are trying to write to
> sockets that have been closed.
> This _may_ occur when the server or the client at the other end has closed
> the connection.
> 
> Are you reporting a bug (that is: do you have problems to use ftp.proxy to
> connect to ftp servers) or are you only complaining about some messages in
> the log file that are not abvious to understand?
> If this is a bug, can you give us further details?
> 
> --
> Greg.
>