Bug 90896
Summary: | please update SMART tools to smartmontools | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | James Ralston <ralston> | ||||||
Component: | kernel-utils | Assignee: | Arjan van de Ven <arjanv> | ||||||
Status: | CLOSED RAWHIDE | QA Contact: | Brian Brock <bbrock> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 9 | CC: | ballen, mitr | ||||||
Target Milestone: | --- | Keywords: | FutureFeature | ||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Enhancement | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2003-07-14 09:19:06 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
James Ralston
2003-05-15 06:45:41 UTC
Created attachment 91689 [details]
patch for /etc/init.d/smartd
this patch makes /etc/init.d/smartd aware of /etc/sysconfig/smart
Created attachment 91690 [details]
sample /etc/sysconfig/smart file
Another solution is to use the smartmontools package: http://smartmontools.sourceforge.net/ The version of smartd in this package give the SMART ENABLE command when devices are registered. It also uses a config file /etc/smartd.conf that permits great flexibility in setup and configuration. So for example if you have a drive that you don't want to enable SMART on, you don't list it in the config file. Okay, I've looked (albeit briefly) at the smartmontools package (thanks for the pointer Bruce), and it seems like the way to go. It would probably make sense to package smartmontools separately, rather than bundling it into kernel-utils. As it is now, the fact that kernel-utils contributes the SMART stuff means that someone who wants to build and install smartmontools themselves either has to rebuild kernel-utils with the SMART stuff removed, or they have to use --replacefiles when installing a smartmontools RPM. Thoughts? Personally I am in favor of having smartmontools be a separate package from the kernel-utils package. But this may have ramifications that I am unaware of, and so I'm not sure if it is the "right thing" to do. Other people are more qualified to decide this than I am. Cheers, Bruce |