Quote from: xeroc on November 16, 2014, 12:54:42 PM
My nodes are running in screen .. all of them ... maybe i can find some time to read into tmux soon .. theres a nice split-screen feature in tmux!

I use tmux for everything. Recommended.

My nodes are running in screen .. all of them ... maybe i can find some time to read into tmux soon .. theres a nice split-screen feature in tmux!

Many thanks, guys :)

Quote from: wackou on November 15, 2014, 08:26:11 PM
I suggest you use either screen(1) or tmux(2) (recommended) to run the client in. These act as persistent shell sessions in which you can run the client and to which you can attach/detach your terminal, which allows you to take command of your client as if you'd never disconnected. Some would argue that those tools have archaic or non-intuitive default bindings, but really you only need to know a couple of shortcuts to be able to enjoy the power and ease-of-use that they bring, there are lots of tutorials on the web that can help you get started in 5-10 minutes with them.

This also has a nice side effect which is that if for whatever reason you lose connection with your server while working on a remote session, this doesn't crash the client because of it but leaves the client running as if you'd just walked away from keyboard. Whenever you get your connection back, you can re-attach to your session and resume what you were doing as if nothing ever happened. Which is quite nice :)

(1) http://en.wikipedia.org/wiki/GNU_Screen
(2) http://en.wikipedia.org/wiki/Tmux

Agreed, screen or tmux are excellent and a must have. I run my feeds on one screen session and client on another. I haven't set up your delegate monitoring tools yet as I haven't gotten enough votes to be active anyways, but that would make a good candidate for a 3rd session.

I suggest you use either screen(1) or tmux(2) (recommended) to run the client in. These act as persistent shell sessions in which you can run the client and to which you can attach/detach your terminal, which allows you to take command of your client as if you'd never disconnected. Some would argue that those tools have archaic or non-intuitive default bindings, but really you only need to know a couple of shortcuts to be able to enjoy the power and ease-of-use that they bring, there are lots of tutorials on the web that can help you get started in 5-10 minutes with them.

This also has a nice side effect which is that if for whatever reason you lose connection with your server while working on a remote session, this doesn't crash the client because of it but leaves the client running as if you'd just walked away from keyboard. Whenever you get your connection back, you can re-attach to your session and resume what you were doing as if nothing ever happened. Which is quite nice :)

(1) http://en.wikipedia.org/wiki/GNU_Screen
(2) http://en.wikipedia.org/wiki/Tmux

http://wiki.bitshares.org/index.php/Delegate/How-To

delegate how to :)

Preparing my delegate, I'm at a bit of a loss for how to launch the bitshares client, unlock the wallet and set the unlock time to something decent via the command line.

I need to nohup the process in order for it to keep running when the bash session ends, but if I do that I cannot type any commands in, and there appears to be a very limited set of command line parameters which the client reads as it starts up?