How to turn off hot-reloading of 2.1.9

[sergeevabc]

Dear @jedisct1,

Previously, the announcement of the new version of DNSCrypt caused joy and interest in finding out how the lives of privacy-concerned people would change for the better. But now it's just scary to look at the news, because there are more and more unexpected features that hardly fit into the existing workflow.

Specifically, v2.1.9 introduced a hot-reloading of config files. As a result, memory consumption increased from 26 MB top to 36 MB and growing. CPU has become more noticeable: it wakes up much more often from a low-power mode, which is accompanied by an unpleasant sound. And I'm worried that some app may change those config files in the background, and it'll take me a while to realize there's a problem.

I tried to find a flag or an option in the TOML settings file to turn this feature off, but no luck there.

What can be done? Roll back to 2.1.8?

[jedisct1]

Yes, roll back to 2.1.8.

[sergeevabc]

It seems that the problems reported earlier have been fixed.
In particular, hot reloading has been rewritten and disabled by default.

Bonus: dnscrypt_v2.1.12_win7x64.zip

[cyberboh]

Did you compile dnscrypt for windows 7? If so, may you update it in the future?

[sergeevabc]

Re: @cyberboh

I do compile DNSCrypt for Windows 7 x64 because that's my OS of choice for the foreseeable future. And I can share binaries. The question is how best to organize the process. I usually create an issue in a Github repo with some Go-based app, name it “Windows 7 build”, close it and then upload new binaries there. Owners treat this favorably, do not object. However, I am not sure that this approach will suit Frank Denis, who does not like when new messages are added to closed issues.

[cyberboh]

@sergeevabc Thank you for compiling it. I also still using Windows 7 X64, I am glad to see there is dnscrypt binary latest version that still working for it.
Maybe you can forks the project and maintain regularly rather than create and close issue in the discussion.
If you fork it, you can host the file on your github repo, so you can maintain easily.
This just my opinion, rest is up to you. Once again, thank you for being maintain dnscrypt for Windows 7, very much appreciated. :)

[daverof]

@sergeevabc v2.1.9 has barely been out for an hour, cut the guy some slack and try to appreciate the massive amount of work that has gone into this.

There was no need for your emotive tone - if you have a query, simply report it and leave out the sob story as the world doesn't revolve around you.

[sergeevabc]

Dave, you're too late to preach as my head is already gray and I have 30 years of bug hunting under my belt. And if such a person is still in a hurry to report a problem without singing sugar odes, it is because the problem is urgent. And it did not arise out of thin air, but as a result of a change in the development process, when more attention is paid to questionable experiments and less attention is paid to testing. Fortunately, at least the code has already been fixed, thereby protecting the developer from the curses of thousands of users who would otherwise have faced increased consumption of system resources. As for hard work, it causes calluses and aches in the bones — the longshoremen at the port will tell you a lot about it. And here we are witnessing the result of a person's creativity in his free time. And the witnesses have the right to leave any feedback, otherwise the discussion function would simply be disabled in the repository.

[jedisct1]

If you can, try compiling and testing the current code in Git.

It supports a different way to watch for file changes, and there's an option to enable/disable hot reloading.

[sergeevabc]

Frank, indeed, it works way better with those recent changes.