Daniel Ouellet wrote:
Alexander Hall wrote:
Daniel Ouellet wrote:
Alexander Hall wrote:
from inetd(8):
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 256.
Not sure how this would be presented then.
So, should I conclude that it should be
tftp dgram udp wait.6000, max.1024 root /usr/libexec/tftpd
Or something like that?
No. The ".6000" part is the max suffix, so the above is not
syntactically correct.
If what you want is at most 1024 servers per minute, ``wait.1024''
should do it.
Then it that case this is the limit that apply to tftpd and the -R apply
to the inetd that start this tftpd then as I already have wait.6000 as
above, but keep getting deny connections, but keeping it as is and
restarting inetd with -R 1024 fix that so far.
That would conclude they do not represent the same thing and something
should be clarify in the man page then, or I don't read it properly, but
looks like you come to my previous conclusion as well, but doesn't react
like this.
May be someone else can provide more details may be?
From reading the fabulous source (/usr/src/usr.sbin/inetd/inetd.c; look
for "toomany"), I can only conclude that they (-R and [.max]) indeed
work as I had guessed, i.e. -R changes the default from 256 to whatever
and that the [.max] suffix allows you to specify it for each specific
service, if needed.
Are you sure that there is no other service that is affected by the -R
switch that you had not thought of?
/Alexander
