Following is a patch that modifies smartd so that
ataSmartEnable is actually called. In the current code
the function is erroneously dereferenced instead of
called, so it 'succeeds' because the function address
is non-NULL but ataSmartEnable is never actually
performed. I'm no SMART expert, but I'd question the
necessity of this call-- smartctl can toggle the
enable/disable option and perhaps smartd ought to have
a 'force' option to override the default set in the
device, otherwise honor the drive settting.
Log in to post a comment.