Author

Topic: bitcoind startup process changed? (Read 760 times)

hero member
Activity: 518
Merit: 500
r00t-dev
July 27, 2014, 06:27:16 AM
#2

Looked through the changelogs and couldn't really see anything, except one mention that RPC calls would be separated from bitcoind sometime in the future.  Anyway, has there been a chance recently (ie. v0.9.2+) in the startup process?  Previously, I would just run "bitcoind -daemon", and all would hum along just fine.

Now though, that doesn't seem to work, because if I kill that SSH connection, things like "blocknotify" seem to stop working.  I've resolved this with using "nohup bitcoind -daemon &", and that seems to keep it going just fine even after the SSH session.  Just curious, has anything changed in that regards, and is there anything else I should be aware of?

Thanks!



not that i know.

have you launched the daemon inside a new screen-session?
sr. member
Activity: 318
Merit: 251
July 26, 2014, 01:57:55 PM
#1

Looked through the changelogs and couldn't really see anything, except one mention that RPC calls would be separated from bitcoind sometime in the future.  Anyway, has there been a chance recently (ie. v0.9.2+) in the startup process?  Previously, I would just run "bitcoind -daemon", and all would hum along just fine.

Now though, that doesn't seem to work, because if I kill that SSH connection, things like "blocknotify" seem to stop working.  I've resolved this with using "nohup bitcoind -daemon &", and that seems to keep it going just fine even after the SSH session.  Just curious, has anything changed in that regards, and is there anything else I should be aware of?

Thanks!

Jump to: