From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Thu, 27 Dec 2018 15:56:20 +0300 From: Vladimir Davydov Subject: Re: [tarantool-patches] [PATCH v3 1/3] box: get rid of atexit() for calling cleanup routine Message-ID: <20181227125620.2o7xgjts5pmljesm@esperanza> References: <98b93e4fd2d6d6affb4dc191ad5d4e8432ffefaa.1544533138.git.sergepetrenko@tarantool.org> <20181227124355.hmoioqgodmkcjclu@esperanza> <20181227125058.GH18166@chai> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181227125058.GH18166@chai> To: Konstantin Osipov Cc: Serge Petrenko , tarantool-patches@freelists.org List-ID: On Thu, Dec 27, 2018 at 03:50:58PM +0300, Konstantin Osipov wrote: > * Vladimir Davydov [18/12/27 15:45]: > > On Tue, Dec 11, 2018 at 04:24:38PM +0300, Serge Petrenko wrote: > > > Move a call to tarantool_free() to the end of main(). > > > Also instead of breaking the event loop directly when processing a > > > signal start a fiber which can do some work before event loop break and > > > then break the event loop (this will be helpful when on_shutdown > > > triggers are implemented to run them while ev loop active). > > > Only wal_thread_stop() is left in atexit() to make sure we close the > > > journal in case the user exits by typing os.exit() to the console. > > > > I don't understand why you need to do it in the scope of the issue > > you're intending to fix. You can start a fiber from SITERM/SIGINT signal > > handler and run on_shutdown triggers from it without atexit rework, > > right? > > I asked Sergey to refactor our atexit machinery. I want atexit > handlers to be able to run the event loop, all such handlers, not > just the exit trigger. But this isn't what this patch does - it just moves some code from atexit() to the end of main, after the event loop is stopped.