On Thu, 22 Aug 2013, Esmq wrote:
hi,list
i have a program writes logs to a named_pipe, while rsyslog reads the pipe and
forward it to remote server.
as we known, named_piped has a limted size around 64KBytes,
when the program write the logs too excessively, the pipe will be fulled even i
configure rsyslog to poll every second(PollInterval 1).
so i come up with following three solutions:
1) increase the named_pipe size ( only availabe to newer linux kernel and have
to modify the program to tune the pipe size before writing log to it)
2) configure the program to split the logs, writing to multiple named_pipes,
then rsyslog reads multiple named_pipes...(is that reasonable?)
3) set rsyslog PollInterval to 0 (performance hit ?!)
now i just try the third solution(it seems works) , any body have suggestion ?
Using a named pipe, I think #1 is your best choice, followed by #3. I think that
#2 would cause no end of problems.
Is there a reason that you need to use a named pipe instead of writing to a unix
socket like /dev/log? Yes, it means your logs need to be formatted properly, but
if you can do that you gain a LOT.
David Lang
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
