Good day,
Just a quick question- could someone please confirm that this is the correct
xinetd configuration (or not) for hpa-tftp?
We've noticed that, when under moderate load hpa-tftpd resides in memory,
even after there are no connections or even if xinetd is shut down. Under
light load the server goes away after each connection, as desired.
Thanks in advance!
service tftp
{
socket_type = dgram
protocol = udp
wait = yes
user = root
log_on_success += USERID
log_on_failure += USERID
server = /usr/sbin/hpa-tftpd
server_args = -s /tftpboot
disable = no
}
===========================Darren Gamble
Planner, Regional Services
Shaw Cablesystems GP
630 - 3rd Avenue SW
Calgary, Alberta, Canada
T2P 4L4
(403) 781-4948
Hi, Darren Gamble <Darren.Gamble at sjrb.ca> schrieb am 22.02.02:> Just a quick question- could someone please confirm that this is the correct > xinetd configuration (or not) for hpa-tftp?don't know too much about xinetd, but seems correct.> We've noticed that, when under moderate load hpa-tftpd resides in memory, > even after there are no connections or even if xinetd is shut down. Under > light load the server goes away after each connection, as desired.tftp-hpa (in recent versions) uses the short daemon mode. So the server remains for some minutes (default: 15 minutes) while no tftp request arrives. Try '-t 30' and the server process will exit after 30 seconds. Maybe you also have some hanging tftp connections, and you see some leftover connections that try to deliver the next packet. These should quit after the tftp timeout, and usually they'll do. These only handle this specific transfer, so there won't be any interaction with different tftp transfers. Regards, Josef ________________________________________________________________ Keine verlorenen Lotto-Quittungen, keine vergessenen Gewinne mehr! Beim WEB.DE Lottoservice: http://tippen2.web.de/?x=13
Good day, Thanks for your reply. I didn't see this option in the documentation, but, it seems to be behaving as expected now. =) ===========================Darren Gamble Planner, Regional Services Shaw Cablesystems GP 630 - 3rd Avenue SW Calgary, Alberta, Canada T2P 4L4 (403) 781-4948 -----Original Message----- From: Josef Siemes [mailto:jsiemes at web.de] Sent: Friday, February 22, 2002 5:22 AM To: DarrenGamble; syslinux at zytor.com Subject: Re: [syslinux] hpa-tftp with xinetd Hi, Darren Gamble <Darren.Gamble at sjrb.ca> schrieb am 22.02.02:> Just a quick question- could someone please confirm that this is thecorrect> xinetd configuration (or not) for hpa-tftp?don't know too much about xinetd, but seems correct.> We've noticed that, when under moderate load hpa-tftpd resides in memory, > even after there are no connections or even if xinetd is shut down. Under > light load the server goes away after each connection, as desired.tftp-hpa (in recent versions) uses the short daemon mode. So the server remains for some minutes (default: 15 minutes) while no tftp request arrives. Try '-t 30' and the server process will exit after 30 seconds. Maybe you also have some hanging tftp connections, and you see some leftover connections that try to deliver the next packet. These should quit after the tftp timeout, and usually they'll do. These only handle this specific transfer, so there won't be any interaction with different tftp transfers. Regards, Josef ________________________________________________________________ Keine verlorenen Lotto-Quittungen, keine vergessenen Gewinne mehr! Beim WEB.DE Lottoservice: http://tippen2.web.de/?x=13