Hi,

I just double checked. You are right. But, I seem to have not correctly presented the problem.

The issue doesnt seem to be when I pull out and plug in on the client side. The problem is when the cable is pulled out 
on the server side. We waited for 20 mins but the client did not timeout.

Santosh

> Despite the interface flag. The TCP (that FTP is implemented on) suppose to 
> detect such case, and timeout ... in 10 minutes. If you wait that long, you 
> should see FTP client report that.
> 
> TCP is designed (defiend) like this, try to overcome any network shortage, and
>  recover automaticlly.
> 
> -xtang
> 
> 
> -----Original Message-----
> From: Santosh Kumar [mailto:community-noreply@qnx.com]
> Sent: Sun 26/07/2009 01:13
> To: technology-networking
> Subject: FTP Client does not timeout after media is unplugged
>  
> Hi,
> 
> We have implemented an application that invokes the FTP client via system call
> . Once the an FTP transfer is completed or failed we get a response back from 
> the FTP client. However this fails for one scenario. During transfer of the 
> file if the transfer is interrupted by pulling out the ethernet cable, the FTP
>  client is kind of "hung" and never returns. It does not even recover after 
> the ethernet cable is plugged back in.
> 
> We do not see a change in the "RUNNING" flags of the Ethernet interface if we 
> plug in or plug out the ethernet cable. We are using QNX 6.4.0 with the GA 
> release of io-pkt that came along with it. The processor we use is MPC 8572. 
> We run QNX in SMP mode. We use the TSEC PHY which is controlled by the 
> ethernet driver provided by QNX. We use the in-net version of the driver with 
> shim.
> 
> What we expect is some kind of an error response if the ethernet media is 
> plugged out. How can we achieve this?
> 
> Thanks,
> Santosh
> 
> 
> 
> _______________________________________________
> 
> Technology
> http://community.qnx.com/sf/go/post34587
> 
>