From: Torne <torne@wolfpuppy.org.uk>
Subject: Bug in gpape's ipsvd
Date: Sun, 04 Jul 2004 19:08:44 +0100 [thread overview]
Message-ID: <9B82FDA0C3DCED5F1C8737D9@[192.168.10.2]> (raw)
[-- Attachment #1: Type: text/plain, Size: 709 bytes --]
tcpsvd interprets an instruction of 'C0' for a particular host as meaning
'no connections', whereas the documentation states that this should allow
unlimited connections up to the global limit. This situation only arises
when there is a global per-host concurrency limit which is being overridden
for particular IPs. Patch below.
--- tcpsvd.c.orig 2004-07-04 19:00:56.000000000 +0100
+++ tcpsvd.c 2004-07-04 19:01:15.000000000 +0100
@@ -172,7 +172,7 @@
}
else ac =IPSVD_DEFAULT;
- if (phcc > 0) {
+ if (phccmax > 0) {
if (phcc > phccmax) {
ac =IPSVD_DENY;
if (phccmsg) {
--
Torne (torne@wolfpuppy.org.uk)
Wolf puppy, coder and social engineer.
[-- Attachment #2: Type: application/pgp-signature, Size: 187 bytes --]
next reply other threads:[~2004-07-04 18:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-04 18:08 Torne [this message]
2004-07-08 18:05 ` Gerrit Pape
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='9B82FDA0C3DCED5F1C8737D9@[192.168.10.2]' \
--to=torne@wolfpuppy.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).