|Main Archive Page > Month Archives > syslog-ng-users archives|
Sorry for the extra posts. Can't think straight today:))
Are you using flow-control? I went back to your first couple of posts and
didn't see it mentioned.
At first I thought it was for only TCP, but then I found it in the manual
under log path flags and it didn't say it was only for TCP.
f l o w - control- Enables flow-control to the log path, meaning that
syslog-ng will stop reading messages from the sources
of this log statement if the destinations are not able to process the
messages at the required speed. If
disabled, syslog-ng will drop messages if the destination queues are full.
If enabled, syslog-ng will only
drop messages if the destination queues/window sizes are improperly sized.
On Thu, Apr 28, 2011 at 6:56 PM, Zeek Anow <firstname.lastname@example.org> wrote:
> Mike - You asked earlier about if anyone knows a way to figure out when our
> pieces of junk starts to get pegged:)) Check this out:
> I know it is for TCP, but you can still probably get some use out of it.
> The only thing I question is why he never changed the log_iw_size.**
> Hope it helps..
> On Thu, Apr 28, 2011 at 12:46 PM, Zeek Anow <email@example.com> wrote:
>> That would be great. Thanks!!
>> On Thu, Apr 28, 2011 at 11:33 AM, Gergely Nagy <firstname.lastname@example.org>wrote:
>>> Zeek Anow <email@example.com> writes:
>>> > Thanks. Will do.
>>> > What is git:))
>>> A version control system :]
>>> Come to think of it, it's probably easier for everyone if I prepare a
>>> tarball from Bazsi's latest version, with bells & whistles included.
>>> I'll try not to forget, but if I don't post back with a link within a
>>> day, please remind me O:)
>>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
>>> FAQ: http://www.campin.net/syslog-ng/faq.html
Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng