On Fri, 4 Dec 2015, Manoj Kumar wrote:
Hi,
I am using Rsyslog v 8.14.0 with an external module written in Python and
integrated via omprog. I want rsyslog to spawn only single instance of
external module and therefore use forcesingleinstance configuration. The
behavior I see is that
- rsyslog spawns a process for client.py, then this process becomes
inactive and rsyslog spawns another process. And the old one keeps
lingering.
- I do not want a lingering inactive process as it is consuming extra
memory.
How can I get rid of inactive lingering process. Thank you for your help.
local1.* action(type="omprog" binary="/home/ubuntu/client.py"
queue.filename="elmo" queue.type="linkedlist" forcesingleinstance="on")
e.g. top output
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
5605 syslog 20 0 78.3m 25.6m 4.5m S 0.0 0.3 0:15.66
/usr/bin/python /home/ubuntu/client.py
5600 syslog 20 0 75.4m 22.7m 4.5m S 0.0 0.3 0:10.34
/usr/bin/python /home/ubuntu/client.py
hmm, I only see one instance of things running on my systems (and I don't do the
forcesingleinstance), if you do ps -ef |grep client.py does it show that they
are both children of the same process? or are they children of different
processes?
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.
