Summary
Exceeding the timeout during restic init --repo causes an error.
Is it possible to configure the timeout via an environment variable (e.g., RESTIC_TIMEOUT_INIT) to handle such edge cases?
Motivation / Use case
I am using a Buffalo NAS (TS-WVHL/R5) that supports only SMB 1.0.
The device is old, and there is no way to update the SMB protocol.
Proposed solution
Add environment variable (e.g., RESTIC_TIMEOUT_INIT)
Impact
None
Summary
Exceeding the timeout during
restic init --repocauses an error.Is it possible to configure the timeout via an environment variable (e.g.,
RESTIC_TIMEOUT_INIT) to handle such edge cases?Motivation / Use case
I am using a Buffalo NAS (TS-WVHL/R5) that supports only SMB 1.0.
The device is old, and there is no way to update the SMB protocol.
Proposed solution
Add environment variable (e.g., RESTIC_TIMEOUT_INIT)
Impact
None