Hello, thanks for your help. I check my syslog file and this is what I get with max-connections(10): Jul 15 12:54:17 s_all@logserver syslog-ng[20780]: Number of allowed concurrent connections exceeded; num='10', max='10' I just change to max-connections(500) and it works great. I will read more about ulimit option. Best regards. -----Mensaje original----- De: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] En nombre de Gergely Nagy Enviado el: lunes, 18 de julio de 2011 15:28 Para: Syslog-ng users' and developers' mailing list Asunto: Re: [syslog-ng] max-connections(1000) Daniel Maher <dmaher@milestonelab.com> writes:
On 07/15/2011 01:46 PM, Gergely Nagy wrote:
However, this limit can also be raised, using ulimit (and perhaps poking into various configuration files, such as /etc/security/limits.conf).
It may be worth noting that limits.conf is only respected if PAM is configured to use it, and the session is spawned by something that uses PAM; in general, things started by init.d at boot-time do not meet that criteria.
Yep, that's why I mentioned it in brackets only, and suggested ulimit as the primary means of achieving the goal ;) -- |8] ______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq