[syslog-ng] [Bug 190] syslog-ng with TCP source, fails to shutdown properly, and generates core dump

[bugzilla at bugzilla.balabit.com]

https://bugzilla.balabit.com/show_bug.cgi?id=190





--- Comment #12 from Marvin Nipper <marvin.nipper at stream.com>  2012-08-29 17:13:21 ---
Alright... sort of depressing... as I thought I had this one behind me.  I've trashed the old stuff, so I'll have to rebuild it, and redeploy it, but that's
life, I suppose.

I only want to have to do this once, so I want to get this right (and certainly, get you what you need).  Not actually being a Solaris developer, and also not
having ever needed to use truss, I'll be somewhat in the dark here.  This is what I'm _thinking_ that I need to do:
truss -aef -o /var/opt/truss.out \
  /usr/local/sbin/syslog-ng -F -f /etc/syslog-ng/syslog-ng.conf \
         -p /var/run/syslog-ng.pid \
         --persist-file=/usr/local/syslog-ng/syslog-ng.persist

The intent being to exactly mirror my production options.  I just tried that with my working version of the executable, and it seems to work (i.e. syslog-ng
still works, and truss generates data in the output file).  And I am _guessing_ that you only need this thru the point where the core file appears??

I just need to know if these options (for truss) suffice, or if you are looking for something else?

Let me know.  Thanks.


-- 
Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.