mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Angelo Borsotti <angelo.borsotti@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: processes/threads monitor
Date: Sat, 31 Jan 2009 22:57:36 +0100	[thread overview]
Message-ID: <541298b90901311357o593a4339t46a44e8933bb1a6b@mail.gmail.com> (raw)

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

             reply	other threads:[~2009-01-31 21:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-31 21:57 Angelo Borsotti [this message]
2009-02-01  3:14 ` Valdis.Kletnieks
2009-02-01  6:50 ` Willy Tarreau

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=541298b90901311357o593a4339t46a44e8933bb1a6b@mail.gmail.com \
    --to=angelo.borsotti@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®