SUMMARY: How many connection can I have to a tcp() source? 10? Why? I have been experiencing a problem with a syslog-ng (1.4.11) server seemingly only allowing 10 connections to a tcp() source. A quick tour of the code found the offending code at line 341 in afinet.c: self->super.max_connections = 10; Elsewhere in the file I see this (with code missing): if (c->num_connections >= c->max_connections) { #FAIL TO CONNECT }else{ #SUCCESSFULLY CONNECT } Unless this is not the code to handle tcp() sources, I think I've found what I need to change in order to fix this. My question is to Balazs, or anyone else with insight into the design of this daemon: Why is the limit set to 10? I want to change it, potentially to something very high (100 sounds about right for now), what impact is this going to have? JetNet Logo Chris Sibbitt Operations Development 333 Preston St, 3rd floor Ottawa, Ontario K1S 5N4 Phone (613) 237-5995, ext228 Fax (613) 237-9002
On Mon, Nov 12, 2001 at 05:34:41PM -0500, Chris Sibbitt wrote:
SUMMARY: How many connection can I have to a tcp() source? 10? Why?
I have been experiencing a problem with a syslog-ng (1.4.11) server seemingly only allowing 10 connections to a tcp() source. A quick tour of the code found the offending code at line 341 in afinet.c:
self->super.max_connections = 10;
it's limited because otherwise it'd be easy to mount a DoS attack against the logger host. you can change this limit run-time without changing the source with the max-connection option to tcp(): source src { tcp(max-connections(100)); }; -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
participants (2)
-
Balazs Scheidler
-
Chris Sibbitt