[erlang-questions] how to start and stop erlang daemon

[Roman Galeev]

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 Tue, May 15, 2018 at 2:39 PM, Max Lapshin <max.lapshin@REDACTED> wrote:

> Hi.
>
>
> I've written a bit unstructured thoughts about seamless start and stop of
> erlang daemon:
>
> https://medium.com/@max.lapshin/how-to-start-and-stop-
> erlang-daemon-3fd988777ab3
>
> In short:
>
> 1) validate config before launching
> 2) control that daemon has started
> 3) find a way to notify why it hasn't started
> 4) use several ways to stop it and to ensure that it has stopped
>
>
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
>


-- 
With best regards,
     Roman Galeev,
     +420 702 817 968
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20180515/1aaf0b2a/attachment.htm>