From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lj1-f182.google.com (mail-lj1-f182.google.com [209.85.208.182]) (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 2C296469710 for ; Mon, 25 May 2020 15:17:20 +0300 (MSK) Received: by mail-lj1-f182.google.com with SMTP id b6so20549688ljj.1 for ; Mon, 25 May 2020 05:17:20 -0700 (PDT) From: Cyrill Gorcunov Date: Mon, 25 May 2020 15:17:05 +0300 Message-Id: <20200525121715.21216-1-gorcunov@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [Tarantool-patches] [PATCH 00/10] lua/log: add an ability to setup logger without box.cfg{} List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: tml Cc: Alexander Turenko In the series we add an ability to configure logger early without calling box.cfg{}. The syntax is the same as in box.cfg{} call. There was an idea to implement something similar via triggers but I think this will require a way more efforts and code redesign, so at first lets stick to simplier solution. Cyrill Gorcunov (10): core/say: drop redundant declarations core/say: drop vsay declaration core/say: do not reconfig early set up logger lua/log: declare say_logger_init and say_logger_initialized lua/log: put string constants to map lua/log: do not allow to set json for boot logger lua/log: use log module settings inside box.cfg lua/log: allow to configure logging without a box lua/log: update log status via box.cfg call test: use direct log module src/box/lua/load_cfg.lua | 28 ++++++-- src/lib/core/say.c | 18 +++-- src/lib/core/say.h | 8 +-- src/lua/log.lua | 135 ++++++++++++++++++++++++++++++++--- test/app-tap/logger.test.lua | 28 ++++++-- 5 files changed, 189 insertions(+), 28 deletions(-) -- 2.26.2