From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 13177 invoked from network); 6 Sep 2020 15:54:03 -0000 Received: from alyss.skarnet.org (95.142.172.232) by inbox.vuxu.org with ESMTPUTF8; 6 Sep 2020 15:54:03 -0000 Received: (qmail 20143 invoked by uid 89); 6 Sep 2020 15:54:27 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Received: (qmail 20136 invoked from network); 6 Sep 2020 15:54:27 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=Rhn58TRIvpYihDHCsoTp9RuceVoOKOE78DHqxryRyiY=; b=rYY0tcWhxqfGOlIaxSiV5L+NxD0FE4YYT4eP3WB1FOylMOsaCy5SuouugohDPOqKuC L6t80XeZuxC2mhPZ6JD7So9LDbSiIZCYzB+HikEXDT7jRsyjOtw3Q9UFXkJWwdLANZxh LZn5dz+1x9J1UYkSYUyjBB/pRLBJBCnCJGBS2ltIjXsRKMruyYNjmjozUBD3YGDsFd/U bPe068uIhjgH5/TzInTquZY824r1Ucs2V05AWgFZVaxlqPXLOiNUPteqfzZce3f9qaJ3 a+HrXJcMBkvUmHr9WbhpIff7529vPJJ90iKEkrJq/9ZLyDlHDa2CY3U22N1ItYyblA/x DjLQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=Rhn58TRIvpYihDHCsoTp9RuceVoOKOE78DHqxryRyiY=; b=pErr5Qc3v41624sIg8oGNQwQNuBZoVZcGaRkx401TbkrZFAHhP2EA5gNnmaig12sqm GgaoqwCGp4YQKHZ0daTtJ9fZBX78Zkr2B+qbgiLeQA6lQr+/GDQsVAhwpvSPo1QV6SDh d5DJrdBJUDB3FpXpezGdJNyF+iZmep/RlGXe0nFiDHoLs6p1HC/sBvqFVAZFqSomHd+Z v9P+brfBiI0ZaPH0MRuIkXb4VRqZP1XPA54wBwVbJknsnr9kqV9UPPhCJEI3AyG/hFpL HoXnf+L5ujDAPr4J0BYo7r5wAofFPMsIF0ZJOPljA61cnO4JZTPwnVybIoiSaCQbbn1Q VnXw== X-Gm-Message-State: AOAM530olkmzxPBRC9ShocQA3WQjld13w7LCj0+p1Zb6OEsPuzvB5age Y2B5xooYSuALdWYjE6QxcOujp4AeYXIsoStv7QXDT/8tRSsPcg== X-Google-Smtp-Source: ABdhPJwq2unaTM6rWzjqzqPY5Kgc8pRXJCXZDTIeTzLRKXBNLo1dKlQYQO9QQCHZGo78ZpIa16JdwGaROQVyxIVIHVw= X-Received: by 2002:a05:6214:178c:: with SMTP id ct12mr15509699qvb.12.1599407639384; Sun, 06 Sep 2020 08:53:59 -0700 (PDT) MIME-Version: 1.0 References: <408ccc80-aa66-66cb-12ae-f29e6aba6cc7@sholland.org> In-Reply-To: From: Rio Liu Date: Sun, 6 Sep 2020 11:53:48 -0400 Message-ID: Subject: Re: Update early logger logging path after remounting root as rw To: supervision@list.skarnet.org Content-Type: multipart/alternative; boundary="00000000000032579f05aea71c0d" --00000000000032579f05aea71c0d Content-Type: text/plain; charset="UTF-8" Thanks for all the replies :) > Your requirements of saving logs from /run/uncaught-logs and (mentioned > later) batch-producing `producer-for'/`consumer-for' files can be > automated using slew: . (Other > encapsulations of s6/s6-rc also exist, but I am the author of slew ;) > Yeah I'll need to look around and take inspirations from all the s6-rc wrapper/scripts. Thanks for sharing. 1) Bring up a second service reading from the same > /run/service/s6-svscan-log/fifo pipe, and once the new logger is ready, > bring > down the old s6-svscan-log service (from a oneshot depending on the new > logger). > During the transition, log lines could go to either service, but nothing > would > be lost. I like the idea of reading /run/services/s6-svscan-log/fifo from a new logger instance, I might try it and see how it works. In 66 this is written as /run/66/log/0/current, and I have user/root > copy it after a shell is executed, this helps when I would change > something and it is not booting right on the next boot, I can compare > the before after. Part of 66 booting procedure is to activate tty12 as > early as possible, instead of the insecure sulogin that appears in > runit. From tty12 you can read that log and mount things manually and > change/fix what is wrong. You can also decrease/increase verbosity in > that log. tty12 is a special setup in 66 where root can't login, only a > user can, a security measure I find as a great idea. > Have verbose log in tty12 is a great idea, I'll see how 66 does it and maybe implement it in my setup. --00000000000032579f05aea71c0d--