From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id C466C25346 for ; Mon, 12 Aug 2019 12:10:30 -0400 (EDT) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YAsddXb_2nHz for ; Mon, 12 Aug 2019 12:10:30 -0400 (EDT) Received: from smtp58.i.mail.ru (smtp58.i.mail.ru [217.69.128.38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTPS id 80882245EC for ; Mon, 12 Aug 2019 12:10:30 -0400 (EDT) From: =?utf-8?B?0JPQtdC+0YDQs9C40Lkg0JrQuNGA0LjRh9C10L3QutC+?= Subject: [tarantool-patches] Re: [PATCH] Make `tarantoolctl start` work withiout box.cfg in init script Date: Mon, 12 Aug 2019 19:10:16 +0300 Message-ID: <5529040.u0ZvfgNaiR@localhost> In-Reply-To: <20190812132452.GB9305@atlas> References: <20190809081022.1237-1-m.melentiev@corp.mail.ru> <5668311.GLNk2tWfSB@localhost> <20190812132452.GB9305@atlas> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3648815.moDHPqNV4L"; micalg="pgp-sha256"; protocol="application/pgp-signature" Sender: tarantool-patches-bounce@freelists.org Errors-to: tarantool-patches-bounce@freelists.org Reply-To: tarantool-patches@freelists.org List-Help: List-Unsubscribe: List-software: Ecartis version 1.0.0 List-Id: tarantool-patches List-Subscribe: List-Owner: List-post: List-Archive: To: Konstantin Osipov Cc: tarantool-patches@freelists.org, Maxim Melentiev , k.nazarov@corp.mail.ru --nextPart3648815.moDHPqNV4L Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" On Monday, August 12, 2019 4:24:52 PM MSK Konstantin Osipov wrote: > * Georgy Kirichenko [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. --nextPart3648815.moDHPqNV4L Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEFZT35EtIMRTDS5hJnoTdFFzh6LUFAl1Rj2kACgkQnoTdFFzh 6LUfDwf9Hw0xNDZPRDkkUE6lN/XUa4eywETNh+G7d6bgPWB3G7Xjx7LtNttZRqzR IQWeFe6ulIdyV8vhuufP/iqvf02EYc2r4Hob/lSKqzBlBhtvvVWNh+nc70dpdUW6 z2eO4Y6dtAZlbGa4v684NNuciPADxhZ1NvzDXEU8/nct+jUmVRUl9AmZIVJM2g2p zEs/NcTp39f5I9eDNbQbEgB+/FZGodspUHpikvQgj2Qkj8U57VjN/5tELSZuy5b/ U/NcFwB/CSl0Z2H1ii11Vo4r853vzEdf4uymsfbvxcg1DJ6mVPVqjL1evXHVTgtx V94i/rWrWaggdErRc+5E8e3akKiCIQ== =rkQR -----END PGP SIGNATURE----- --nextPart3648815.moDHPqNV4L--