Tuesday, February 27, 2024
HomeBitcoinIs it potential to run Bitcoin Core (GUI) concurrently bitcoind?

Is it potential to run Bitcoin Core (GUI) concurrently bitcoind?

I am in a really irritating scenario. I used to run Bitcoin Core on Home windows, with out these issues, however ever since I switched to Linux (XFCE), and I in fact have Bitcoin Core (GUI) beginning routinely, I am interrupted after like 5 minutes whereas typing/working by an indescribably annoying GUI field saying “Loading wallets…”. That is regardless of working it with -min to begin minimized and never trouble me. However it does anyway.

This has grow to be so annoying that I have been pressured to take away Bitcoin Core from beginning routinely. As an alternative, I’ll open it solely once I actively must do a Bitcoin switch. However then a brand new downside arises: the blockchain can be many months outdated once I lastly open it up, after which it has to take a seat round for a very long time and sync the blockchain earlier than I can do something with it. Additionally, I can not use its RPC API if nothing is working.

So as a substitute I am now beginning bitcoind at boot, so that it’s going to run within the background with no GUI and hold the blockchain updated.

However now, there is a new downside: if I begin Bitcoin Core (GUI) whereas bitcoind is working within the background, I get an error saying that it may possibly’t get hold of a lock of the blocks dir or one thing alongside these traces. Clearly, it’s because bitcoind is already engaged on the block dir.

I can “remedy” this by first working a script which calls the RPC API with the “cease” command, in order that bitcoind shuts down safely (killing the method isn’t secure). Then I will open Bitcoin Core (GUI) and begin utilizing it.

However, as you may think about, that is something however a really perfect scenario. I now must each keep in mind to not simply begin the Bitcoin Core (GUI) program once I want it, but in addition to first dig up and run that script to first shut down bitcoind. After which, after I am performed in Bitcoin Core (GUI), I must shut it down and once more begin bitcoind to return to the identical state as earlier than. It simply makes my pores and skin crawl.

Is there some hidden possibility I can ship when opening Bitcoin Core (GUI) in order that as a substitute of attempting to run its personal stuff, it simply “hooks into” the prevailing bitcoind?



Please enter your comment!
Please enter your name here

Most Popular

Recent Comments