linux-kernel - Re: Tracking all signals how to

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 13 Jun 2008 09:27:39 -0400
From:	Mahmoud Hanafi <mhanafi@....com>
To:	"Bart Van Assche" <bart.vanassche@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Tracking all signals how to

Yes I have verified that it was the OOM killer. We always get lots of
messages in the conole log when the oom killer starts. This is a very odd
problem as there are no logs showing what is doing the killing.

May I can wrap the kill() systemcall?


Computer Sciences Corporation
Registered Office: 3170 Fairview Park Drive, Falls Church, Virginia 22042,
USA
Registered in Nevada, USA No: C-489-59

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------

This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery.
NOTE: Regardless of content, this e-mail shall not operate to bind CSC to
any order or other contract unless pursuant to explicit written agreement
or government initiative expressly permitting the use of e-mail for such
purpose.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------




                                                                           
             "Bart Van Assche"                                             
             <bart.vanassche@g                                             
             mail.com>                                                  To 
                                       Mahmoud Hanafi/DEF/CSC@CSC          
             06/13/2008 01:45                                           cc 
             AM                        linux-kernel@...r.kernel.org        
                                                                   Subject 
                                       Re: Tracking all signals how to     
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




On Thu, Jun 12, 2008 at 11:37 PM, Mahmoud Hanafi <mhanafi@....com> wrote:
> We have random nodes experience killing of most daemons( syslog, ssh,
> cron, etc). All these daemons report getting a sigkill or sigterm.
>
> My question.... Is there a way to log all signals and the originator
> pid/proc name.

Did you already have a look in the kernel messages to make sure it's
not an OOM problem ? I do not know of any Linux software that sends
random signals to random processes.

Bart.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/