On Thu, 16 Jul 2015, Risto Vaarandi wrote: > 2015-07-15 23:07 GMT+03:00 David Lang <[email protected]>: > >> On Wed, 15 Jul 2015, Risto Vaarandi wrote: >> >> Hi David, >>> I noticed that sec is running without --notail option, but this causes sec >>> to stay around even after rsyslog has closed the write end of the pipe. I >>> would suggest including the --notail option in the sec command line which >>> causes it to exit when rsyslog closes the pipe (for more information, >>> there >>> is also a relevant entry in the sec FAQ). >>> >> >> Thanks, that will solve the problem of alerting, but it won't give me info >> on what else is going on. >> >> when rsyslog exits, it properly stops sec, and I am not seeing anything in >> the rsyslog logs to indicate what's going on from it's point of view. >> > > Is my understanding correct that you would like to have sec running even > after rsyslog has exited, and have ways to re-establish the connection > between sec and rsyslog when rsyslog starts again? If so, I'd recommend to > use a named pipe (FIFO) instead of a memory based pipe, and run sec > *without* the --notail option on the named pipe. > risto
no, rsyslog does not exit. something is going on that I don't understand that is causing the connection between rsyslog and sec to break. I'm trying to debug it, not just work around it. I dont' really want to have sec run independently, because then I need to create a sepaate watchdog to restart sec if/as needed David Lang ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ _______________________________________________ Simple-evcorr-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/simple-evcorr-users
