# Gavin Andresen
# 2010-12-03 19:49:15
# https://bitcointalk.org/index.php?topic=2060.msg26555#msg26555

I just checked in a minor bug fix / cleanup. @p{par}

The bug:  boolean options/flags were being treated inconsistently.  If you specified -gen=0, that meant (and still means) "do not generate."  But specifying -testnet=0 did the opposite of what you might expect. @p{par}

Now all boolean flags behave the same way; for example: @p{brk}
 -gen  : means generate @p{brk}
 -gen=1  (or gen=1 in bitcoin.conf): means generate @p{brk}
 -gen=0  (or gen=0 in bitcoin.conf): means do not generate @p{par}

... and if you don't specify the option at all, that means "don't." @p{par}

@p{(bf}Check your bitcoin.conf file!@p{bf)}  If you are using anything beside "0" and "1" for boolean options, you need to change.  I had: @p{par}


Code:
rpcssl=true   # THIS IS WRONG!
 @p{brk}
... in one of my bitcoin.conf files.  The correct syntax is rpcssl=1 @p{brk}