It's actually odd this tip about the .conf file is not more widely known
But to truly keep it running 24/7 what you guys do for those cases when the process gets killed for some reason?
Most often it's ram and no swap situation but I guess it happens sometimes on high ram systems too.
So what about those cases?
Any smart trick?
Not pretty, but works: A crontab that starts the process every x Minutes. If bitcoind already runs it will do nothing, but a log entry. Another crontab takes care removing that log file every so often.
Other options include upstart and monit, both of which I had little success on Ubuntu 12.04. My understanding is upstart is working under 14.04. systemd is now availble on 15.04, but I haven't tinkered with that one yet.