Is this config file right? This machine has been in used for a number of years and has gone through many Ubuntu upgrades. There are two different directories, but it uses /srv/tftp.
The serving directory is on my main root volume.
The files in it are symlinks onto a raid volume which is mounted at boot.
/dev/md2p1 on /home type ext4 (rw,noatime,nodiratime)
It must have come up and exited..... No log file and I also greped in the log directory. System thinks it is running but it really isn't. No pid file either.
jonsmirl@terra:/etc/default$ sudo service tftpd-hpa start
start: Job is already running: tftpd-hpa
jonsmirl@terra:/etc/default$
service --status-all
[ ? ] tftpd-hpa
jonsmirl@terra:/etc/init.d$ sudo service tftpd-hpa stop
tftpd-hpa stop/waiting
jonsmirl@terra:/etc/init.d$ sudo service tftpd-hpa start
tftpd-hpa start/running, process 11479
jonsmirl@terra:/etc/init.d$
Maybe confusing between starting as a process vs inetd? I don't care which way it runs.
No log file.
jonsmirl@ terra:/ etc/default$ cat tftpd-hpa
#Defaults for tftpd-hpa
RUN_DAEMON="yes"
OPTIONS="-l -s /tftpboot"
TFTP_USERNAME= "tftp" "/srv/tftp" "0.0.0. 0:69" terra:/ etc/default$
TFTP_DIRECTORY=
TFTP_ADDRESS=
jonsmirl@
Is this config file right? This machine has been in used for a number of years and has gone through many Ubuntu upgrades. There are two different directories, but it uses /srv/tftp.
The serving directory is on my main root volume.
The files in it are symlinks onto a raid volume which is mounted at boot.
jonsmirl@ terra:/ etc/default$ ls /srv/tftp -l florida/ lpc31xx/ arch/arm/ boot/ea3131. dtb florida/ lpc31xx/ arch/arm/ boot/uImage terra:/ etc/default$
total 0
lrwxrwxrwx 1 root root 51 Apr 3 16:15 ea3131.dtb -> /home/apps/
lrwxrwxrwx 1 root root 47 Apr 3 16:16 uImage -> /home/apps/
jonsmirl@
/dev/md2p1 on /home type ext4 (rw,noatime, nodiratime)
It must have come up and exited..... No log file and I also greped in the log directory. System thinks it is running but it really isn't. No pid file either.
jonsmirl@ terra:/ etc/default$ sudo service tftpd-hpa start terra:/ etc/default$
start: Job is already running: tftpd-hpa
jonsmirl@
service --status-all
[ ? ] tftpd-hpa
jonsmirl@ terra:/ etc/init. d$ sudo service tftpd-hpa stop terra:/ etc/init. d$ sudo service tftpd-hpa start terra:/ etc/init. d$
tftpd-hpa stop/waiting
jonsmirl@
tftpd-hpa start/running, process 11479
jonsmirl@
Maybe confusing between starting as a process vs inetd? I don't care which way it runs.