> > What happens to TFTP transfers with your change? Are they terminated > gracefully? Or do they hang around until the server times out and > kills them? > > Andrew > Unfortunately, I don't have any means to check that. Which is why I brought it up as a topic for discussion. Then I realized that it would be easier to discuss if somebody who _did_ have a means to check that checked that, which led to me posting the patch :-)
IIRC, a TFTP server will keep spewing out packets until it has sent the whole file, and will retry and retransmit if the client stops responding. So, it guess it depends on what the TFTP transport stream (implemented in code somewhere in RedBoot) does when it gets a "terminate" call that isn't an abort... Hmmm... looking at the code, I see something that looks like: if (abort) tftp_error_ack(...) else tftp_ack(...) which looks to me like TFTP folks would be getting some sort of similar error message for TFTP transfers. I wonder why I'm the only one whose noticed this? (he asks in a plaintive, "why do these things always happen to me" voice) --wpd
