On Wed, 24 Jul 2002, Mark Neidorff wrote:
> Recently I've started getting a signal 15 error. Is it bad hardware
> that would cause it?
Signal 15 is a SIGTERM (see "kill -l" for a complete list). It's the way
most programs are gracefully terminated, and is relatively normal
behavior. The real question you should be asking is "Who/what is sending
the SIGTERM?"
> Any ideas? More info needed? Could a flaky monitor do this? Flaky
> video card? Failing ram? (Things that go "bump" in the night? <grin>)
If you think it's RAM, try running memtest overnight and see what it says.
Otherwise, you might want to turn on process accounting, start certain
daemons like kdm with verbose debugging and/or stderr redirected to a log
file, or enabling core dumps.
Like I said, terminating if signal 15 is caught is perfectly normal.
Getting a signal 15 out of the cosmic dust is pretty unlikely,
though...something has to be sending it.
--
"The only thing that helps me maintain my slender grip on reality is the
friendship I share with my collection of singing potatoes."
- Holly, JMC Vessel *Red Dwarf*
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
