From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lj1-f194.google.com (mail-lj1-f194.google.com [209.85.208.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id 80BEA46970F for ; Thu, 28 Nov 2019 01:31:33 +0300 (MSK) Received: by mail-lj1-f194.google.com with SMTP id d5so26233149ljl.4 for ; Wed, 27 Nov 2019 14:31:33 -0800 (PST) Date: Thu, 28 Nov 2019 01:31:31 +0300 From: Cyrill Gorcunov Message-ID: <20191127223131.GG2472@uranus> References: <20191126151557.25754-1-sergepetrenko@tarantool.org> <20191126205620.GC23422@atlas> <20191127160751.GF2472@uranus> <20191127215147.GB31812@atlas> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191127215147.GB31812@atlas> Subject: Re: [Tarantool-patches] [PATCH] clear terminal state on panic List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Konstantin Osipov Cc: tarantool-patches@dev.tarantool.org On Thu, Nov 28, 2019 at 12:51:47AM +0300, Konstantin Osipov wrote: > > > > Should not we rather provide some tarantool_atexit() helper > > from where we would call other cleanup and etc routines? > > We already have tarantool_atfork() hook. Not a big deal > > but while the code in question is being modified anyway. > > Why not, still the exit procedure is complicated because of > on_shutdown triggers, so it's important that if there are changes > to it, they are documented in the code, not in cs comments. Yes, putting comment into the code why we're to restore the terminal settings on panic is quite important.