diff --git a/index.html b/index.html index 4521ba9..167b5d2 100644 --- a/index.html +++ b/index.html @@ -88,8 +88,38 @@ For further information, check here.
+There are various ways to stop hushd safely. The best and easiest method is +hush-cli stop +
+ ++The kill or killall command should not be used, it can corrupt your wallet.dat! +The funds won't be completely lost, but they will be very hard to recover and require using +advanced command-line tools to fix, which is as good as lost for many people. The kill +command may have worked for you in the past, but it's a dangerous risk. If you are unlucky and +the wallet.dat is being updated when you type the command, it can cause corruption. So it may +have worked for you in the past, possibly many times, but it's still very risky. +
+ ++In some rare cases it's possible that hush-cli stop will not work, because the Hush RPC +interface is not responding. Hush has a special disk-based solution for this case. Run the following +command on Linux: touch ~/.hush/plz_stop . This will create an empty file and hushd will +notice it withing 120 seconds and stop correctly without risking a corrupt wallet.dat . On other +Operating Systems, find the directory with your wallet.dat file and create a file called plz_stop +in the same directory. The contents of the file do not matter. +
+ +Nodes can be out of sync for seemingly infinite reasons. We suggest reporting the details of +your system, such as Operating System version and hushd version to our Telegram Support. +Make sure to include details such as if you are using hushd directly or SilentDragon and any relevant version numbers. +