search for: sig_name

...ws here, and am open to almost any kind of > suggestion that can be followed-up (as compared to "beats me" which is > where I am now). OK, more information. Found a recipe to cause systemtap to emit a line of text identifying the sender of the SIGKILL. probe signal.send { if (sig_name == "SIGKILL") printf("%s was sent to %s (pid:%d) by %s uid:%d\n", sig_name, pid_name, sig_pid, execname(), uid()) unfortunately, it says the program is killing itself: SIGKILL was sent to myprog (pid:12269) by myprog uid:1000 So,... now I'm wondering how o...

...aws here, and am open to almost any kind of > suggestion that can be followed-up (as compared to "beats me" which > is where I am now). OK, more information. Found a recipe to cause systemtap to emit a line of text identifying the sender of the SIGKILL. probe signal.send { if (sig_name == "SIGKILL") printf("%s was sent to %s (pid:%d) by %s uid:%d\n", sig_name, pid_name, sig_pid, execname(), uid()) unfortunately, it says the program is killing itself: SIGKILL was sent to myprog (pid:12269) by myprog uid:1000 So,... now I'm wondering how o...

...gt; > suggestion that can be followed-up (as compared to "beats me" which is > > where I am now). > > OK, more information. > > Found a recipe to cause systemtap to emit a line of text identifying the sender of the SIGKILL. > > probe signal.send { > if (sig_name == "SIGKILL") > printf("%s was sent to %s (pid:%d) by %s uid:%d\n", > sig_name, pid_name, sig_pid, execname(), uid()) > > unfortunately, it says the program is killing itself: > > SIGKILL was sent to myprog (pid:12269) by myprog uid:1000 >...

Hi all! I'm stuck on something really bizarre that is happening to a product I "own" at work. It's a C program, built on CentOS, runs on CentOs or RHEL, has been in circulation since the early 00's, is in use at hundreds of sites. recently, at multiple customer sites it has started just going away. no core file (yes, ulimit is configured), nothing in any of its (several)