linux-kernel - processes/threads monitor

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

Message-ID: <541298b90901311357o593a4339t46a44e8933bb1a6b@mail.gmail.com>
Date:	Sat, 31 Jan 2009 22:57:36 +0100
From:	Angelo Borsotti <angelo.borsotti@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: processes/threads monitor

Hello,

I wish to be personally CC'ed the answers/comments posted to the list
in response to this posting

In 2004, a thread appeared in the mailing list, stating the need for
some means to
monitor processes and threads. Patches were proposed, and alternatives solutions
hinted. However, the thread ended with no final solution to the problem.
I would like to bring the problem up again.

The need occurs on Linux installations in which there are some process
control applications,
or some continuous sever applications that need some resilience
towards process failures.
When a process providing an essential service terminates, come
"process monitor" would
create it again, restoring the service automatically (and without the
need for human intervention).
Traditionally this has been implemented in a very inefficient way by
having some process
reading periodically the list of running processes (e.g. by execing
"ps") and checking if the
processes providing essential service are still there.
This is clearly very inefficient, and all the more, it needs to be
executed repeatedly polling
processes.
A much more efficient solution would be for the process monitor to be
allowed to wait
for the termination of any processes/threads belonging to a specified list.
Note that this would mean waiting for one among several events to occur.

Are there any solution to this?

-Angelo Borsotti
--
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/