Description:
The README instructs users to download DigiByte Core v7.17.3, but the systemd service example later in the guide references v7.17.2 in the ExecStart path.
Example from README:
ExecStart=/home//digibyte-7.17.2/bin/digibyted ...
However, the earlier installation step downloads:
digibyte-7.17.3-x86_64-linux-gnu.tar.gz
Impact:
Users who follow the guide exactly will end up with a systemd service pointing to a non‑existent directory (digibyte-7.17.2), causing:
• service startup failure
• confusing “file not found” errors
• unnecessary troubleshooting
Suggested Fix:
Update the systemd example to reference the correct version:
ExecStart=/home//digibyte-7.17.3/bin/digibyted ...
Or alternatively, replace the versioned folder with a variable or generic path to avoid future mismatches.
Description:
The README instructs users to download DigiByte Core v7.17.3, but the systemd service example later in the guide references v7.17.2 in the ExecStart path.
Example from README:
ExecStart=/home//digibyte-7.17.2/bin/digibyted ...
However, the earlier installation step downloads:
digibyte-7.17.3-x86_64-linux-gnu.tar.gz
Impact:
Users who follow the guide exactly will end up with a systemd service pointing to a non‑existent directory (digibyte-7.17.2), causing:
• service startup failure
• confusing “file not found” errors
• unnecessary troubleshooting
Suggested Fix:
Update the systemd example to reference the correct version:
ExecStart=/home//digibyte-7.17.3/bin/digibyted ...
Or alternatively, replace the versioned folder with a variable or generic path to avoid future mismatches.