2.0.0 is quite old. I think there are some mem leak fixes in the more recent v2-stable builds (see changelog). I suggest updating (from source) to the current v2-stable (2.0.6 or so, not sure out of my head).
Rainer ----- Ursprüngliche Nachricht ----- Von: "Daniel Anson" <[EMAIL PROTECTED]> An: "[email protected]" <[email protected]> Gesendet: 28.08.08 16:56 Betreff: [rsyslog] Memory vanishes For a bit of background, I have a RHEL5 server acting as an aggregate point to write rsyslog/syslog info to: rsyslog.i386 2.0.0-11.el5 installed rsyslog-mysql.i386 2.0.0-11.el5 installed I am manipulating this data received with a threaded C program. So, in the spirit of testing, I wrote this small code to produce logs so I can test how many messages that can be processed. Here is the code for that program: #include <syslog.h> int main(int argc, char **argv) { int num_syslogs = atoi(argv[1]), i; openlog("syslog_writer", LOG_CONS | LOG_PID, LOG_USER); for(i=0; i < num_syslogs; i++) { syslog(LOG_INFO, "syslog_writer: log number %d", i); } closelog(); return 1; } I run it thusly: ./syslogwriter 300000 After the running of this program, I find that ~30MB of memory just disappear and never reappear. I understand that MySQL and other programs can hold some memory but do end up releasing it. This is not the case, this memory is not freed. I know that I am not using the most current version but I am using a STABLE release. Has anyone seen this behavior before or have an idea why this is happening. I am at a loss. Have I merely reached a limitation point in the number of consecutive logs that can be handled? Thx, Daniel M. Anson Linux Systems Engineer III Rackspace [EMAIL PROTECTED] Office: (210)312-5114 Confidentiality Notice: This e-mail message (including any attached or embedded documents) is intended for the exclusive and confidential use of the individual or entity to which this message is addressed, and unless otherwise expressly indicated, is confidential and privileged information of Rackspace. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at [EMAIL PROTECTED], and delete the original message. Your cooperation is appreciated. _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog
