[4048] in linux-net channel archive
Re: tftp/udp server failing (looping), service terminatedsh
daemon@ATHENA.MIT.EDU (J.D.Coleman)
Fri Aug 16 10:03:48 1996
From: "J.D.Coleman" <J.D.Coleman@newcastle.ac.uk>
To: eb@amazon.com (Eric Benson)
Date: Fri, 16 Aug 1996 09:50:36 +0100 (BST)
Cc: linux-net@vger.rutgers.edu, server-linux@netspace.org
Eric Benson wrote:
> I'm running bootbd and tftpd on Linux serving a bunch of NCD
> X-terminals. It's working fine, except that once in a while I get this
> message in /var/log/messages,
>
> Aug 15 14:28:14 lambada inetd[95]: tftp/udp server failing (looping),
> service terminated
>
> Has anyone else seen this problem? Do you have any idea what's wrong?
>
This is because inetd keeps track of when a server is started and believes
that the server is failing if it starts too many times in a given interval
(60 seconds). If inetd believes the server is failing, it will no longer
start that service and outputs the above log entry. Kill -HUP restarts the
process.
To avoid this, alter your inetd.conf. From the man page (*nix documentation
is kept in man pages - for inetd, type 'man inetd') :
"The fields of the configuration file are as follows:
service name
socket type
protocol
wait/nowait[.max]
user[.group]
server program
server program arguments"
"The optional ``max'' suffix (separated from ``wait'' or ``nowait'' by a dot)
specifies the maximum number of server instances that may be spawned from
inetd within an interval of 60 seconds. When omitted, ``max'' defaults to 40."
Therefore, change your inetd.conf entry from :
tftp dgram udp wait root /usr/sbin/tcpd /usr/sbin/in.tftpd
to something like :
tftp dgram udp wait.60 root /usr/sbin/tcpd /usr/sbin/in.tftpd
If it still fails, increase the value above.
J
--
"The Ravenous Bugblatter Beast of Traal! Is it safe?"
"Oh yes, it's perfectly safe. It's just us who are in trouble!"
--
Wargame (n): battle simulation using painted numbers.
