In message <[email protected]>, David
Lang writes:
>I've started running SEC from rsyslog via omprog and it's running,
>but when it tries to write the dumpfile, nothing happens.
>
>I did a cut-n-paste of the command line (as shown in ps) and ran it from the
>command line and from there it does create the dump file. the dump files are
>set to be written to /var/tmp
>
>I don't know if the problem is with rsyslog, SEC, or RHEL 6.x
>
>so I figured I'd crosspost to both lists to see if anyone had an idea :-)
Does SEC's log file report that the signal was received? You may have
to increase the logging to level 6 to see that.
Have you tried sending another signal to the SEC process and see if it
is received (maybe SIGHUP -> restart)?
I have a feeling that rsyslog is ignoring the signal and that is
causing SEC/perl to ignore the signal as well. From signal(7)
A child created via fork(2) inherits a copy of its parent?s signal dis-
positions. During an execve(2), the dispositions of handled signals
are reset to the default; the dispositions of ignored signals are left
unchanged.
But AFAIK SEC sets handlers for the USR1 and other signals and that
should override any default ignore set by the parent process. So I
don't have an answer.
--
-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.
------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
_______________________________________________
Simple-evcorr-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/simple-evcorr-users
