On Monday, August 12, 2019 4:24:52 PM MSK Konstantin Osipov wrote:
> * Georgy Kirichenko <georgy@tarantool.org> [19/08/12 16:05]:
> > The biggest issue I see we don't have any clue how to control application
> > on each stage of it's life. How could application to report an error or
> > unwanted state right after daemonization (or even after READY=1 written)
> > but before application is really initialized. We do not have even logging
> > here (logger is initialized while box.cfg fired).
> > I think we need a framework which allows to customize and to control
> > application which includes logging and application state.
> 
> There is already such framework and we use it, it's systemd
> socket.

There is completely no problem with systemd because there is nothing to do as 
system already able to daemonize a service and track it's state (including 
starting->started switch).

Out issue stems from a no-systemd environment when user starts service without 
root-privileges and/or on-systemd installations.