[syslinux] Issue with running tftpd-hpa in inetd mode?

[Dan Swartzendruber]

> On 01/30/2014 10:25 AM, Jeffrey Hutzelman wrote:
>>
>> Correct.  Like most UDP-based inetd services, tftpd is intended to be
>> run in 'wait' mode.  When the first request arrives, inetd starts the
>> service but does not read the incoming packet (it can't, because it has
>> no way to pass it along to the server).  After that, inetd ignores that
>> socket until the server exits.  This isn't critical for tftp, but it
>> does help to keep down the number of times the server program is started
>> (an expensive operation) on a busy server.  For some other services, it
>> is critical, because the server must be able to exchange packets with
>> the client on the same port on which the original request arrived.
>>
>
> Actually, it *is* critical for tftp, because there is no sane way to
> handle the strange tftp port handling otherwise.

Yes, it took me some head scratching when I first ran into tftp to grok
the 'i will reply with a different port and the client will then
communicate on that channel not port 69...'