Re: [rsyslog] omprog script left running after rsyslog stopped

> On 2020-06-04 20:00, John Chivian via rsyslog wrote: From the documentation page... [omprog] Executes the configured program and feeds log messages to that binary via stdin. The binary is free to do whatever it wants with the supplied data. If the program terminates, it is re-started. If

Re: [rsyslog] omprog script left running after rsyslog stopped

From the documentation page... [omprog] Executes the configured program and feeds log messages to that binary via stdin. The binary is free to do whatever it wants with the supplied data. If the program terminates, it is re-started. If rsyslog terminates, the program’s stdin will see EOF. The

[rsyslog] omprog script left running after rsyslog stopped

Hello, I am using omprog to send mail logs to my script: mail.* action(type="omprog" name="blacklist" binary="/usr/local/sbin/blacklist.py" template="long-iso") It works well, but I have noticed that when I stop rsyslog, the script is not terminated, but continues running. I can see the

[rsyslog] Question about omstdout: stdout output module (testbench tool)

Hi. In the doc for omstdout is this statement "Please note we do not put too much effort on the quality of this module as we do not expect it to be used in real deployments." But in today's IT is stdout quite often used also in the rsyslog image.

[rsyslog] Configuration syntax error with TLS parameters

Hi, I am trying to enable TLS authentication between source and destination in rsyslog. The TLS authentication is established and working. However I am getting an error when I run `rsyslogd -N1`. The configuration files are: # cat /etc/rsyslog.d/tls.conf global( DefaultNetstreamDriver="gtls"