On 01/20/2018 07:40 AM, Adrian Sevcenco wrote:
On 01/19/2018 03:00 PM, James Hogarth wrote:
Seeing as this is a very unusual request, even to the point prior to
systemd tftpd was run under xinetd rather than its own service, I
think the first question is why?
i don't want (need) a supplementary service (xinetd) to activate and run
and i dont want the tftpd service to be activated automatically
It doesn't use xinetd any more. It uses systemd which is already
running anyway.
What problem are you attempting to solve that you think this is the
solution?
There's good reason for it being a socket based service, even prior to
could you please explain me what is the reason? (beside being
automatically started when an access is requested on 69?)
Most people don't want the tftp server process to be always running. So
it's nice that systemd will answer the socket connect and start the
server only when it is needed.
systemd, so it would be useful understanding what you are trying to
accomplish as an end goal.
see above ... given that the ExecStart line is running as intended, if i
cannot solve this dependency problem i will just do a personaly
mytftp.service and be done with it...
The easiest way to do what you want is to copy
/usr/lib/systemd/system/tftp.service to /etc/systemd and edit it to
remove the socket dependency and add the -l option to the server command.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
