From: Chris Snook <csnook@redhat.com>
To: sk malik <srikrishanmalik@yahoo.co.in>
Cc: LKML1 <linux-kernel@vger.kernel.org>
Subject: Re: Self healing in linux ?
Date: Thu, 16 Aug 2007 16:46:55 -0400 [thread overview]
Message-ID: <46C4B7BF.70305@redhat.com> (raw)
In-Reply-To: <666676.51583.qm@web7614.mail.in.yahoo.com>
sk malik wrote:
> Solaris 10 people are talkin a lot about the
> predictive self healing thing.
>
> Do we have something similar planned/going on for
> linux. Or there is no use of this tecnology ;)
Doing this in-kernel would violate the separation of policy and
mechanism. There's nothing wrong with providing the hooks necessary for
userspace to do this, but it's generally userspace's responsibility to
decide what should be done when a possible problem is detected. I'm
aware of software that does predictive migration with mdadm when smartd
detects a problem. Getting this into users' hands is a distro/vendor
problem, not a kernel development problem.
That said, if you can think of some additional hooks that would really
be beneficial to userspace monitoring tools, by all means send in patches.
-- Chris
prev parent reply other threads:[~2007-08-16 20:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-16 16:13 Self healing in linux ? sk malik
2007-08-16 20:46 ` Chris Snook [this message]
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=46C4B7BF.70305@redhat.com \
--to=csnook@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=srikrishanmalik@yahoo.co.in \
/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