< luke-jr>
user confused because bitcoind stops working when he set a rpcpassword
< luke-jr>
turns out he didn't restart bitcoind
< luke-jr>
not sure we can really fix this
< gmaxwell>
luke-jr: tell users to not set rpcpasswords.
< gmaxwell>
we plan on getting rid of that, so that will solve users following old instructions.
< luke-jr>
gmaxwell: this is beside the point; rpcauth won't do any better
< gmaxwell>
it would be: the utils would still use the cookie auth in that case. so it wouldn't mysteriously stop.
< gmaxwell>
And did the user actually need rpcpassword for anything or were they merely following some instructions online?
< luke-jr>
no idea
< luke-jr>
cookie auth is typically harder to use, so I imagine he was setting it to use it
< luke-jr>
gotta read a file in, and know to reload it & retry if it fails to auth later
< gmaxwell>
right but 'set something and the cli tool stop' goes away, e.g. you can use rpcauth for your remote process but the tools can keep using cookie auth.