• ballen4705's avatar
    Minor change in philosophy: if a SMART command fails or the device · cd4e9dc1
    ballen4705 authored
        appears incapable of a SMART command that the user has asked for,
        complain by printing an error message, but go ahead and try
        anyway.  Since unimplemented SMART commands should just return an
        error but not cause disk problems, this should't cause any
        difficulty.
    
        Added two new flags: q and Q.  q is quiet mode - only print: For
        the -l option, errors recorded in the SMART error log; For the -L
        option, errors recorded in the device self-test log; For the -c
        SMART "disk failing" status or device attributes (pre-failure or
        usage) which failed either now or in the past; For the -v option
        device attributes (pre-failure or usage) which failed either now
        or in the past.  Q is Very Quiet mode: Print no ouput.  The only
        way to learn about what was found is to use the exit status of
        smartctl.
    
        smartctl now returns sensible values (bitmask).  See smartctl.h
        for the values, and the man page for documentation.
    
    
    git-svn-id: https://smartmontools.svn.sourceforge.net/svnroot/smartmontools/trunk@88 4ea69e1a-61f1-4043-bf83-b5c94c648137
    cd4e9dc1