In message <alpine.deb.2.02.1309231617340.25...@nftneq.ynat.uz>,
David Lang writes:
>>> On 09/19/2013 06:16 AM, David Lang wrote:
>>>> 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
Try this:
$ sh
$ trap '' USR1
$ sec (cut and paste of command line mentioned above)
$ kill -USR1 <sec PID>
$ exit
I have a sneaking suspicion that something in SEC/perl isn't restoring
the signal handler if it's set to ignore in the parent process. What
the sequence above should do it ignore USR1 in the shell. Then you
test the SEC USR1 signal handiling.
SEC uses the $SIG{} array to set the signal handlers, I am not sure if
the POSIX::sigaction stuff operates differently or is $SIG{} is
sigaction under the hood..
>enabling the log file shows ongoing activity, but it does not show anything
>when the USR1 is sent to the pid.
That's telling me that USR1 is being ignored somewhere in the process
chain. Can you confirm/deny that USR1 is ignored by the signal
handling in rsyslog?
--
-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
_______________________________________________
Simple-evcorr-users mailing list
Simple-evcorr-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/simple-evcorr-users
