< vault711> hey
< 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.
< luke-jr> oh, rpcauth doesn't disable cookies? :o
< luke-jr> don't think I was aware of that
< gmaxwell> yea, since it has its own username(s) it's pretty sensible that it doesn't. and using both is nice.
< luke-jr> yeah, makes sense
< bitcoin-git> [bitcoin] grazcoin opened pull request #9975: 0.13 bitcore (0.13...0.13-bitcore) https://github.com/bitcoin/bitcoin/pull/9975
< bitcoin-git> [bitcoin] grazcoin closed pull request #9975: 0.13 bitcore (0.13...0.13-bitcore) https://github.com/bitcoin/bitcoin/pull/9975
< bitcoin-git> [bitcoin] sdaftuar opened pull request #9977: QA: getblocktemplate_longpoll.py should always use >0 fee tx (master...2017-03-gbt-longpoll-test) https://github.com/bitcoin/bitcoin/pull/9977