>>>>> On Wed, 22 Mar 2006 14:44:42 +0100, Marcus Rueckert <[EMAIL PROTECTED]> >>>>> said:
Marcus> if you use tcpwrapper every connection gets logged. Marcus> without tcpwrapper this only happens if "-a" is specified at the Marcus> commandline. i dont think this is really intended. We had a discussion on the irc channel about this. I'm sort of on the fence. Functionally, yes there is a difference between the -a switch and tcp_wrappers support. Either one turns on output of address logging. The tcp wrappers code was done a very very long time ago and it's been this way for a while. Thus the options as I see it: 1) do as the patch suggests and change behavior and turn off logging output when tcp_wrappers is enabled but -a isn't. This *is* a behavior change. But it's not one I care much about so I'm fine with it. Note that this will turn on double logging of received packets I think, since it forces users to use -a which means they'll get the existing logging plus the newer one. (I didn't read the code to double check this) 2) make a new ds_boolean tag and turn it into a --long argument and config token and use that and split the functionality between -a (log requests received by the demon) and the tcp_wrappers part of the agent (log requests accepted by tcp_wrappers). I'm ambivalent but I mentioned on IRC it likely needs discussion if we wanted to go with #1 since it was a behavior change. -- Wes Hardaker Sparta, Inc. ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
