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] [thread-next>] [day] [month] [year] [list]

Message-ID: <e2e108260806122245xb2fdd36teb2f265317370875@mail.gmail.com>
Date:	Fri, 13 Jun 2008 07:45:22 +0200
From:	"Bart Van Assche" <bart.vanassche@...il.com>
To:	"Mahmoud Hanafi" <mhanafi@....com>
Cc:	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/