Syslinux - Jul 2014 - tftp-hpa 5.2 testing & checking the setup

I had this problem fixed by setting the ownership of the root tftp
directory, "must be set to nobody as this is the default user ID setup
by tftpd" as specified in this tutorial
http://blackfin.uclinux.org/doku.php?id=setting_up_a_tftp_server

However, I do not know if the ownership set to nobody is essential
with Fedora because SELinux requires it or if it is a general good
practice for any linux distro.

I still havent figured how I can monitor in real time and check logs
of tftp service and socket and xinetd on Fedora like distros

On 07/14/2014 05:52 AM, raincatsdogs at me.com wrote:
> I had this problem fixed by setting the ownership of the root tftp
> directory, "must be set to nobody as this is the default user ID setup
> by tftpd" as specified in this tutorial
> http://blackfin.uclinux.org/doku.php?id=setting_up_a_tftp_server
> 
> However, I do not know if the ownership set to nobody is essential
> with Fedora because SELinux requires it or if it is a general good
> practice for any linux distro.
> 
> I still havent figured how I can monitor in real time and check logs
> of tftp service and socket and xinetd on Fedora like distros
It is, in fact, absolutely horrific practice and a very bad idea.
"nobody" should never own anything (and, in fact, it is generally
better
to split up the nobody user and have separate anonymous users, "tftp"
and so on.)

	-hpa