John Coman wrote: > Mine came out like this: > #tftp dgram udp4 wait nobody /usr/sbin/tcpd /usr/sbin/in.tftpd
The leading # indicates that this entry has been disabled. So you must have a stand-alone instance of a TFTP service running, if it is working as you indicate below. The 'lsof' command the other poster mentioned should help you track down which process it is that's providing the service. In any case, you'll want to review the setup steps you've taken so far, and possibly revert some of the changes you made, such as modifying rc.local. I'd recommend running your TFTP service via inetd, rather than as a stand-alone daemon. It's more efficient for something that is used rarely. > --tftpd-timeout 300 --retry-timeout 5 --mcast-port 1758 --mcast-addr > 239.239.239.0-255 --mcast-ttl 1 --maxthread 100 --verbose=5 As I recall these are redundant with the atftpd defaults, and thus unnecessary, but the atftpd package seems to set things up that way. > /var/lib/tftpboo Seems you've dropped the "t" on the end. I assume that's just a cut-and-paste error in the email. > I am not sure what xinetd does but the only time I ran it was while I was > following the instructions. Perhaps it runs a startup, not sure. xinetd is an enhanced version of the inetd super daemon. It provides a few extra features that aren't necessary for what you're attempting to do. It normally starts up when the system boots. You should be able to run 'aptitude install openbsd-inetd' to get the stock inetd installed. Aptitude will point out the conflict with xinetd and prompt you to remove it. > As far as I know it is setup for /tftpboot. Your experiment seemed to prove that out. Running 'ps auxww | fgrep tftp' might also show you the command line with that path, if you do indeed have a stand-alone TFTP service running. > I get: > Transfer successful: 3648805 bytes in 16 seconds, 1824402 bytes/s > File size reports 3,625,504 bytes OK, good. You should be able to move on to examining other causes for your mvpmc boot failure. Are you using version H or newer MVP hardware? If so, have you set up a TFTP server running on the high numbered port, as indicated in my last post. (The guides on the wiki ought to cover this in more detail.) >> Verify that the size of the file matches the file on your server. If this >> gives you an error, and the cause isn't obvious, examine the logs. Try: > > No errors other than the small difference in file sizes. Small difference between what I posted and what you saw? Or between what you saw and the file on your server? It should be precisely identical to the file on your server. -Tom ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Mvpmc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mvpmc-users mvpmc wiki: http://mvpmc.wikispaces.com/
