[prev in list] [next in list] [prev in thread] [next in thread] 

List:       syslog-ng
Subject:    [syslog-ng]reading debug output
From:       Nate Campi <nate () campin ! net>
Date:       2004-12-28 0:27:38
Message-ID: 20041228002738.GE21568 () campin ! net
[Download RAW message or body]

I have syslog-ng (1.6.4) running as "syslog-ng -d -v" and I happen to
know that messages are buffering up, because I defined a TCP endpoint
where there's nothing listening. 

I can't tell from the debug output what the buffer looks like (how full
it is), is it possible to tell or is there no way to know?  Well, no way
except failed connection messages on internal() and the eventual STATS
messages telling of dropped messages of course.

TIA
-- 
Nate

"A computer will do what you tell it to do, but that may be much
different from what you had in mind." - JOSEPH WEIZENBAUM, quoted in
Time

_______________________________________________
syslog-ng maillist  -  syslog-ng@lists.balabit.hu
https://lists.balabit.hu/mailman/listinfo/syslog-ng
Frequently asked questions at http://www.campin.net/syslog-ng/faq.html

[prev in list] [next in list] [prev in thread] [next in thread]