On Mon, 17 Jan 2011 10:50:25 +0100, Jonas Smedegaard <dr@jones.dk> wrote:
> On Mon, Jan 17, 2011 at 12:03:53AM -0500, micah anderson wrote:
> >On Mon, 10 Jan 2011 21:31:39 +0100, Jonas Smedegaard <dr@jones.dk> wrote:
> >> I consider adding a shell wrapper looking something like this:
> >>
> >> set -e
> >> umask=077
> >> basedir=~/.bitcoin
> >> dbfile="$basedir/DB_CONFIG"
> >> cfgfile="$basedir/bitcoin.conf"
> >> [ -d ~/.bitcoin ] || mkdir ~/.bitcoin
> >> [ -e "$dbfile" ] || echo 'set_flags DB_LOG_AUTOREMOVE' > "$dbfile"
> >
> >the above scares me a little, because someone might have put their own
> >db config into their DB_CONFIG, and the above would overwrite it,
> >everytime they start the daemon.
> >
> >> [ -e "$cfgfile" ] || perl -le 'print"rpcpassword=",map{(a..z,A..Z,0..9)[rand 62]}0..9' > "$cfgfile"
> >
> >nice, but again, wont this run each time bitcoind is started, thus
> >making a new rpcpassword every time?
>
> The frontmost [] means "test for this, and if not, then...".
Of course, I read that wrong!
> Does it still scare you?
No, I am not frightened now that I am no longer ignorant!
> >For fun, I just committed a few things to the collab-maint repository:
> > . examples/bitcoin.conf
> > . bitcoind(1) and bitcoin.conf(5) man pages
> >
> >but I am not so sure what the right way to install the man pages are,
> >maybe cdbs does it magically? Check it out and please correct it if its
> >wrong.
>
> Nice!
>
> Did you hardcode the manpages or generate (at least the bitcoind one)
> using help2man?
Well, I used help2man to give me a template, but it wasn't very good, so
I mostly did manual work on it.
> Oh well, I'll have a look at it.
>
> Oh, and please pretty please add your name as uploader. I would looove
> this to be a teamwork between us - even if you might go busy on me for
> years at a time ;-)
Will do.
m
Attachment:
pgpeNnY3G05yR.pgp
Description: PGP signature