Recommend how to run bitcoind in a production environment #7111

(To be added to the docs)

Suggestions should probably call a script (or insert notification preference here) when bitcoind has crashed/shutdown unexpectedly (SIGINT could probably be ignored ideally).

A basic loop in the face of zero disk space can be highly destructive (ping @luke-jr, you mentioned this somewhere), plus, it may just end up repeatedly restarting/crashing. It could also mean you're giving an adversary infinite tries to get an attack right.

If this is worthwhile, probably worth adding it to https://bitcoin.org/en/full-node#what-is-a-full-node as well.

As pointed out by @laanwj, maybe even just a link to https://mmonit.com/monit/ (or something similar) would be exceptionally useful for many.

Probably something along the lines of https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-monit for bitcoind would be great, with an added notification example (email?)

~I'm willing to write up some basic monit configurations [at some point] and hopefully get some feedback in regards to this. If anyone has some recommendations, feel free to post them here.~~

There are specific problems that bitcoind faces compared to typical service configurations, and it'd be nice to encapsulate some of that with some nice plug-and-play options for users that haven't done this before.

Haven't [and likely won't] had the time to do this, closing unless someone else wants to re-open.