[smartmontools-support] Captive mode timeout?

[Jim Garrison]

On 2/10/2022 5:10 PM, James wrote:
> 
> 
> On 2022-02-10 19:43, Jim Garrison via Smartmontools-support wrote:
>> Given disk sizes today, there probably isn't a single drive that could
>> run "-t long -C" within the timeout.  A 4TB drive (WD4003FFBX) can't
>> even run -t short within the timeout.
>>
>> I see an old issue #303 (https://www.smartmontools.org/ticket/303) from
>> 8 years ago closed WONTFIX.
>>
>> Is captive mode basically no longer meaningful?
> Is that waiting for it to finish?
> I don't think that mode is useful.
> I start a test and look at the result when it is done.

I guess then the answer to my question is that captive mode is no longer
useful or meaningful.

I could see a use for it if the test was being invoked from a script,
where it would be simpler to just wait for the command to finish instead
of having to parse the output to determine how long to wait... but I
guess the use case is marginal.

Thanks