user8710: I'm using Ubuntu 12.04. 
I've tested several scripts that try to get bitcoind running on startup but none have worked out for me.
I'm getting a little bit desperate because I can't even get bitcoind running once I exit my SSH session.
Any clues on how to get bitcoind running once I exit the SSH session?
Best Regards,

user6226: You could use screen or a similar tool like tmux or byoblu. 
Otherwise use the NOHUP command. 
nohup is a POSIX command to ignore the HUP (hangup) signal. The HUP signal is, by convention, the way a terminal warns dependent processes of logout.
Output that would normally go to the terminal goes to a file called nohup.out if it has not already been redirected.
nohup is a low-level utility simply configuring a command to ignore a signal. As seen below, nohup is very far from being a full-featured batch system solving all the problems of running programs asynchronously.

$ nohup abcd &
$ exit

Alternatives:
The screen or tmux command can also detach a process from the current shell. It allows to reattach to the process later on.
e.g. the following call will run somescript.sh detached from SIGHUP and in the background:

$ screen -A -m -d -S somename ./somescript.sh &

https://en.wikipedia.org/wiki/Nohup
My advice is to learn to use screen (or tmux) so you can later re-attach the process to the main shell and interact with it.

8710: <p>I'm using Ubuntu 12.04. </p>

<p>I've tested several scripts that try to get bitcoind running on startup but none have worked out for me.</p>

<p>I'm getting a little bit desperate because I can't even get bitcoind running once I exit my SSH session.</p>

<p>Any clues on how to get bitcoind running once I exit the SSH session?</p>

<p>Best Regards,</p>
 6226: <p>You could use screen or a similar tool like tmux or byoblu. 
Otherwise use the NOHUP command. </p>

<p>nohup is a POSIX command to ignore the HUP (hangup) signal. The HUP signal is, by convention, the way a terminal warns dependent processes of logout.
Output that would normally go to the terminal goes to a file called nohup.out if it has not already been redirected.
nohup is a low-level utility simply configuring a command to ignore a signal. As seen below, nohup is very far from being a full-featured batch system solving all the problems of running programs asynchronously.</p>

<blockquote>
  <p>$ nohup abcd &amp;</p>
  
  <p>$ exit</p>
</blockquote>

<p>Alternatives:
The screen or tmux command can also detach a process from the current shell. It allows to reattach to the process later on.
e.g. the following call will run somescript.sh detached from SIGHUP and in the background:</p>

<blockquote>
  <p>$ screen -A -m -d -S somename ./somescript.sh &amp;</p>
</blockquote>

<p><a href="https://en.wikipedia.org/wiki/Nohup" rel="nofollow">https://en.wikipedia.org/wiki/Nohup</a></p>

<p>My advice is to learn to use screen (or tmux) so you can later re-attach the process to the main shell and interact with it.</p>
