Can't get tftp to start (errors different to other forum posts!)
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Can't get tftp to start (errors different to other forum posts!)
I'm trying to get a tftp server set up on Mandriva, so I can get an embedded ARM board to boot from the Mandriva host.
I have installed tftp server; the GUI services program tells me tftp is started on demand (whatever that means!). Despite many attempts I can't get it to start at all. I've tried this:
/etc/init.d/xinetd restart
which gives the error:
Stopping xinetd [FAILED]
Starting xinetd/bin/bash: xinetd: command not found
[FAILED]
I assume that means that somewhere in the xinetd script there's a command it can't get at? Maybe that's the tftp server?
If I do:
ps -ef | grep tftp
I can definitely see it [tftp] not running.
My /etc/xinetd.d/tftp looks like this:
# default: off
# description: The tftp server serves files using the trivial file transfer \
# protocol. The tftp protocol is often used to boot diskless \
# workstations, download configuration files to network-aware printers, \
# and to start the installation process for some operating systems.
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
}
Which seems, from other postings I've seen here, to be correct.
I have read numerous web pages, including posts here and it would seem I'm doing the right thing. I am guessing there's a problem in something the xinetd script is trying to invoke. However, looking at the script, I am lost as to what most of it means!
As an aside, I assume that the image I want to transfer to the ARM board, I should put into /var/lib/tftpboot?
Is it a fair assumption that if my Mandriva host receives a tftp request then I should be able to see the tftp running with a "ps -ef"?
Also, is there a way of looking at what traffic has come in on a particular ethernet port? For example, I have two ethernet ports and I'm trying to get the embedded ARM board to tftp into 192.168.0.6, which is what I have set my eth1 card up as with a static address? Therefore I'd like to have a look to see what I've had in on eth1. That was I could see whether uboot on my ARM board is really sending the request out correctly.
ps -ef |grep tftp should indeed reveal the connection. My vsftp is started by inetd; see output below where the first ps gives the output when I'm connected and the second one when I disconnected.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.