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=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 13530 invoked from network); 6 Sep 2020 10:36:34 -0000 Received: from alyss.skarnet.org (95.142.172.232) by inbox.vuxu.org with ESMTPUTF8; 6 Sep 2020 10:36:34 -0000 Received: (qmail 16426 invoked by uid 89); 6 Sep 2020 10:36:58 -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 16419 invoked from network); 6 Sep 2020 10:36:58 -0000 X-Virus-Scanned: Debian amavisd-new at disroot.org Subject: Re: Update early logger logging path after remounting root as rw DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1599388589; bh=0XzjrlROCxstBpoYP1uUFIA8oQCwif/SMCVzsyijJgs=; h=Subject:To:References:From:Date:In-Reply-To; b=Z08A5zVJ9pvWesIGpUklozth3L2gRpxPiwbqJ2QhSGq9E/V7/vFPD7AxsfZiqcMYu urTKg3azicR35R99B8/1J6m0yp39La4fm4lGG1jFMhenlb/mtyMoQP0EpSG6+rBwnv GpmpAM9+U9TDUxdj+am3zdv7bdwDXzdzQ3y9iSCKCfv7F4uUUFy+VjuMuyEDcjUXgb Zx3KsAQKBOWOHbb7NtqppbgG1fABtVEvUCEWqorQN4gqXSo710T4i3QKC4Y+RCWeq/ 0FRQYXDr8ysUqLZnu7hKN4t9yNeMq71y5yS+eS7Wd81tda1jWADwjJ+xGQHcZZuaEl MJm2GfnrUP2Mw== To: supervision@list.skarnet.org References: <408ccc80-aa66-66cb-12ae-f29e6aba6cc7@sholland.org> From: yianiris Message-ID: Date: Sun, 6 Sep 2020 13:36:25 +0300 Mime-Version: 1.0 In-Reply-To: <408ccc80-aa66-66cb-12ae-f29e6aba6cc7@sholland.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit The way I understand the importance of the catch-all log is to be able to debug the system that fails to boot. It is writing a log in /run even before a real filesystem is mounted. At this point the system should give access to this file even if root is not mounted as rw yet. There may be many ways to have this copied to a root fs, which means it is already mounted rw, and by this time it seems as the system doesn't have a problem booting, so this log is of little use to getting it to boot. 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. If tty12 isn't accessible, that means the uncaught-log isn't, and I don't think there is anything in the system that could have copied that log into something else. So, if you can have it copied and saved is usually when you don't need it, but when you do need it it can't be copied. I hope this makes sense to someone other than me :)