Go to the directory /etc/xinetd.d
There all the services controlled by xinted reside. If tftp is being controlled by xinetd, then you will find a configuration file specific to it. As Frantisek said, disable=NO should be there if it is xinetd controlled. If not, then disable=YES

In other words, try to check netstat while you put xinetd or tftp on the side of grep. In my experience, I have seen that due to another service listening on the same port, the legit ftp service is not running.

Since we are not getting the logs, it is kinda hard to guess. From the strace, it can't be guessed what is going on. But if the line you mentioned is the only line in strace, then probably something is going very awry. That line is the first line of output that always comes if you attach strace to a running process. Was the right hand value of the line a zero or something else?

Also, I am guessing this problem only appears during transfer of file. If you do a service check on tftp, what appears? Can you toggle the status of the service and try? Also, toggle the tftp status keeping xinetd on and off and find whether that makes any difference?

- Soham


On Sat, Oct 8, 2011 at 3:53 PM, Frantisek Hanzlik <franta@hanzlici.cz> wrote:
Aaron Gray wrote:
..
>> I guess, it is running as a xinetd controlled daemon, if so, is there anything else
> listening on the tftp port?
>
> How do I ascertain this ?

- "netstat" utility should be display xinetd daemon listening at udp
port 69 :

# netstat -a -n -p --ip|grep 69
udp        0      0 0.0.0.0:69                  0.0.0.0:*
1595/xinetd

- and You "/etc/xinetd.d/tftp" should be as (note "disable = no"):

service tftp
{
       disable = no
       socket_type             = dgram
       protocol                = udp
       wait                    = yes
       user                    = root
       server                  = /usr/sbin/in.tftpd
       server_args             = -s /var/lib/tftpboot
       per_source              = 11
       cps                     = 100 2
       flags                   = IPv4
}

- and xinetd daemon must be running; on F14 you can use command:
service xinetd status
and on F15 command:
systemctl status xinetd.service