What you described works manually.
Basically, the service is not started on reboot even though I've enabled it. So
I don't know what 'enabling' a service means.
Since tftp-server installs /etc/xinetd.d/tftp, is it hinting that it should be
started via xinetd? Do I need to install xinetd or is systemd so do-it-all,
know-it-all that it's taken over xinetd's functions?
I've tried the obvious steps. I'm working my way through all the permutations
(however illogical) to see what works. Obviously, enabling a systemd service
does not necessarily start the service on reboot. When does enabling a service
not enable it?
I wanted to test an application I wrote and I've spent 3 hours trying to
configure the system so it will let me.
Systemd is really too much.
On 9/11/18 9:35 AM, Hinz, David (GE Healthcare) wrote:
If you're asking what I think you're asking:
systemctl enable tftp # This adds a symlink for tftp into the (target? Milestone? One of
those), equivalent to saying "/etc/rc2.d is done, now let's go to rc3.d".
systemctl start tftp # This tries to start it
systemctl status tftp # This gives you success, or debug information if it
didn't work.
If I missed your question entirely, then can you word it differently?
Dave Hinz
On 9/11/18, 9:32 AM, "owner-scientific-linux-us...@listserv.fnal.gov on behalf of Ken
Teh" <owner-scientific-linux-us...@listserv.fnal.gov on behalf of t...@anl.gov>
wrote:
I need help with how to enable tftp service. I am trying to get something
done
and I have no patience for systemd's convoluted logic.
The tftp-server installs
(1) /etc/xinetd.d/tftp
(2) tftp.socket (what's this?)
(3) tftp.service
Manually, I can start the service and everything works. But enabling the service
stays disabled or indirect. Enabling the socket does not start the service
on
reboot. Do I need xinetd or does systemd deprecate xinetd?
Geez! I miss the old days when Unix was simple.
