From: grarpamp <grarpamp@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: [Bitcoin-development] RPC and signals - processing priority
Date: Fri, 15 Jun 2012 16:55:41 -0400 [thread overview]
Message-ID: <CAD2Ti2-wqMwxJ6iU-z2kYjUjc4GkYMo0dWjL4rcPr2DjODfirQ@mail.gmail.com> (raw)
While happily processing these:
received block ...
SetBestChain: new best=... height=... work=...
ProcessBlock: ACCEPTED
bitcoind very often refuses to answer rpc queries such as getinfo/stop,
or signals such as kill/ctrl-c. It even registers:
ThreadRPCServer method=getinfo/stop
in the debug log. But the action doesn't happen as expected.
Shouldn't it be checking and processing all user interrupts like
once per block and doing the chain in the background?
How do busy commerce servers deal with this poor rpc handling?
Is there a way to increase the priority of user scheduled tasks?
What's going on? Thanks.
next reply other threads:[~2012-06-15 20:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 20:55 grarpamp [this message]
2012-06-16 7:04 ` Wladimir
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAD2Ti2-wqMwxJ6iU-z2kYjUjc4GkYMo0dWjL4rcPr2DjODfirQ@mail.gmail.com \
--to=grarpamp@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox