This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Problems when aborting tftp transfers
- From: Andrew Lunn <andrew at lunn dot ch>
- To: ?yvind Harboe <oyvind dot harboe at zylin dot com>
- Cc: ecos-discuss at sources dot redhat dot com
- Date: Mon, 2 Aug 2004 15:01:34 +0200
- Subject: Re: [ECOS] Problems when aborting tftp transfers
- References: <1090406873.15766.20.camel@famine>
On Wed, Jul 21, 2004 at 12:47:53PM +0200, ?yvind Harboe wrote:
> I'm seing problems when aborting tftp transfers:
>
> - With CYGSEM_NET_TFTPD_MULTITHREADED == 0, a subsequent tftp transfer
> after an aborted tftp transfer can get "stuck" since the main tftp
> server loop is receiving stale packets and hence e.g. _write_file() is
> invoked for the terminated tftp transfer session(there can be as many as
> a dozen outstanding stale packets, hence tftp can take a *really* long
> time to return to normal operation). Q: Is
> CYGSEM_NET_TFTPD_MULTITHREADED == 0 working as intended for aborted tftp
> transfers?
>
> - I'm not sure this is a problem or just the way tftp works. When I set
> CYGSEM_NET_TFTPD_MULTITHREADED==1, tftp works even if I abort transfers,
> but the current tftp transfer session on the eCos end does not return to
> the main tftp server loop until the current transfer session has
> exhausted its retries.
I don't follow what you are taking about here. Could you give some
more details, describe how you produce the problems, what goes wrong
and how you would expect it to act.
Thanks
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss