]> arthur.barton.de Git - ngircd-alex.git/commitdiff
Don't set a penalty time when doing DNS lookups
authorAlexander Barton <alex@barton.de>
Fri, 21 May 2010 21:47:28 +0000 (23:47 +0200)
committerAlexander Barton <alex@barton.de>
Tue, 29 Jun 2010 20:55:27 +0000 (22:55 +0200)
The logic isn't as described in the source and intended by this code:
ngIRCd doesn't wait for the asynchronous resolver process until the set
penalty time is over, but until the forked process terminates or the
initial connection timeout (= PongTimeout) triggers.

So don't set the penalty time at all and remove the wrong comment.

src/ngircd/conn.c

index dff9336f65af4c2f7e581185d1396047e7b5d92b..0d82d530b80733dc23fd18e827b5142bfd06ca54 100644 (file)
@@ -1382,11 +1382,6 @@ New_Connection(int Sock)
                Resolve_Addr(&My_Connections[new_sock].proc_stat, &new_addr,
                             identsock, cb_Read_Resolver_Result);
 
-       /* ngIRCd waits up to 4 seconds for the result of the asynchronous
-        * DNS and IDENT resolver subprocess using the "penalty" mechanism.
-        * If there are results earlier, the delay is aborted. */
-       Conn_SetPenalty(new_sock, 4);
-
        Account_Connection();
        return new_sock;
 } /* New_Connection */