Open unsystemizer opened 9 years ago
This is independent from the conf file you mention. Nonetheless it is not supposed to do this...
Could it be the reason was that you ran the installer before with autostart activated? You then ran it a second time with autostart disabled and it did not get removed. I have it fixed by cleaning up any previous autostart links in https://github.com/namecoin/nmcontrol/pull/100
I don't think I did (I have Namecoin Core and NameGUI, don't think I had tried NMControl before).
start=0
in the config file, I suppose?)start=0
, there is start=1
, although it's marked-outRegardless of autostart links, shouldn't the config file setting matter? (What I mean by this is, if autostart link starts NMControl, NMControl should check the config file and if it says start=0
, it should exit)
The start
settings in the conf files are only relevant for the specific plugins, not for NMControl as a whole.
About to close...
v0.8:
When installing I chose not to install NMControl as service, but it still tried to start:
I looked at service-dns.conf and I have this:
Does
;
mean this is the default? It seems the installer always sets this to 1, or doesn't specifically setstart=0
even when instructed.Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.