IMO an application should validate configuration itself and loudly refuse to start if the required configuration is inconsistent or absent. Daemons start/stop/control procedures afaik are defined by each and every Linux distro out there already (iirc mostly by guessing/checking pids), how beam.smp is different?
On 18 May 2018 at 07:15, Max Lapshin <[hidden email]> wrote:
> How can you signal to system administrator that config is invalid?
We do a mixture of the following:
- Erlang node refuses to start; upstart (or systemd) or monit send an
error email and attempt to restart it.
- Erlang node reports an error; lager backend turns that into an error email.
- Erlang node fails to do whatever it's supposed to do; external check
notices (nagios can't connect to port, end-to-end smoke test fails,
e.g.), notifies administrator.