Hi,
OK, but how do we know the state? I'm sorry but we don't have any idea
about software RAID (don't use it either). If you tell us what what value to
look.
Actuallly, I don't like software RAID. We want to forget about our servers
once they are installed and I believe software RAID will make startup less
robust in case of a powerdown (yes I know, we should use a UPS but the
client won't use it). That's why our next work will be to implement ReiserFS
on e-smith. Has anybody some experience with this?
See you.
----- Original Message -----
From: "Trevor Ouellette" <[EMAIL PROTECTED]>
To: "Smith, Jeffery S (Scott)" <[EMAIL PROTECTED]>; "'Jeff Martin'"
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, September 04, 2001 11:10 PM
Subject: RE: [e-smith-devinfo] E-smith monitor suggestions
> Maybe we could start with software RAID status monitoring? It's pretty
well
> WORKING or NOT_WORKING status.
>
> Trev.
>
> > -----Original Message-----
> > From: Smith, Jeffery S (Scott) [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, September 04, 2001 12:06 PM
> > To: 'Jeff Martin'; [EMAIL PROTECTED]
> > Subject: RE: [e-smith-devinfo] E-smith monitor suggestions
> >
> >
> > > -----Original Message-----
> > > From: Jeff Martin [mailto:[EMAIL PROTECTED]]
> > > Sent: Tuesday, September 04, 2001 1:38 PM
> > > Subject: Re: [e-smith-devinfo] E-smith monitor suggestions
> > >
> > >
> > > Not sure if it's possible but it would be nice to have some
> > > kind of a> > > sent via email if problems were found.
> >
> >
> > Sending the email is the easy part. The problem with this type of thing
is
> > defining what exactly a "problem" is. For example, on systems with very
> > small drives, free space below 20% is a problem. For others it is not a
> > problem until you hit 5%. Other folks prefer to set those levels as
actual
> > free space rather than percentages. And so on. Then there is the issue
of
> > "warning" vs "alert" messages, or "code yellow" vs "code red" problems,
or
> > other severity mapping schemes. There is even the issue of what
> > to call them
> > -- Warning/Alert, Code Green/Yellow/Red, Level 1/2/3, Low/Med/High, etc.
> >
> > These issues can be solved by allowing user specified trigger
> > levels for one
> > or multiple severity levels, plus the appropriate labeling and message
> > content, etc. But then you have the problem of maintaining the
> > configuration
> > for the alert system. Sometimes the configuration management for an
> > application can be a larger task than the application itself!
> >
> > I'm not saying it can't be done or wouldn't be valuable if it were
done --
> > I'm only cautioning that the number of options are many and depending
upon
> > how many are pursued the task may not be simple at all.
> >
> > Scott
> >
> > --
> > Please report bugs to [EMAIL PROTECTED]
> > Please mail [EMAIL PROTECTED] (only) to discuss security issues
> > Support for registered customers and partners to [EMAIL PROTECTED]
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > Archives by mail and
> http://www.mail-archive.com/devinfo%40lists.e-smith.org
>
>
>
> --
> Please report bugs to [EMAIL PROTECTED]
> Please mail [EMAIL PROTECTED] (only) to discuss security issues
> Support for registered customers and partners to [EMAIL PROTECTED]
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> Archives by mail and
http://www.mail-archive.com/devinfo%40lists.e-smith.org
>
--
Please report bugs to [EMAIL PROTECTED]
Please mail [EMAIL PROTECTED] (only) to discuss security issues
Support for registered customers and partners to [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
