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.0 required=5.0 tests=none autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 31264 invoked from network); 18 Oct 2021 09:18:59 -0000 Received: from 4ess.inri.net (216.126.196.42) by inbox.vuxu.org with ESMTPUTF8; 18 Oct 2021 09:18:59 -0000 Received: from oat.nine.sirjofri.de ([5.45.105.127]) by 4ess; Mon Oct 18 05:10:15 -0400 2021 Received: from sirjofri.de ([95.90.219.31]) by oat; Mon Oct 18 10:51:26 +0200 2021 Date: Mon, 18 Oct 2021 08:51:26 +0000 (UTC) From: sirjofri To: 9front@9front.org Message-ID: <029d4fad-b2fb-4d9b-a0e2-577574e6950c@sirjofri.de> In-Reply-To: <28C9A8BDB0039016DE60A0FCC1FCBFAF@antares-labs.eu> References: <28C9A8BDB0039016DE60A0FCC1FCBFAF@antares-labs.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Correlation-ID: <029d4fad-b2fb-4d9b-a0e2-577574e6950c@sirjofri.de> List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: ISO-certified general-purpose blockchain framework Subject: =?UTF-8?Q?Re:_[9front]_Re:_[9front]_Re:_[?= =?UTF-8?Q?9front]_Dealing_with_log_files=E2=80=A6?= Reply-To: 9front@9front.org Precedence: bulk I can imagine some mq-like fileserver mounted at /sys/log, which can have some ctl file for settings like rotation, as well as dumping some configured logs to actual files for long-time storage, maybe including filters. To explain this idea a little more: Imagine a smb service with this log fileserver. In /sys/log you can see the full log of the server, but only the full log of the day. After mounting the full service (mount /srv/logsrv /mnt/logsrv) you could access the full log, but in a filtered form, e.g. only failed logins to the smb server. The log in /sys/log only exists in memory, (fast writing, ...) The log in /mnt/logsrv is backed by actual files you can dump to a venti or something like that. The logsrv fileserver could also contain some internal log rotation with multiple files and auto-deletion, the interface for the services wouldn't change at all (they just write to an mq-like file in /sys/log). Of course a heavy tool like that makes sense only in a larger network, but it's interesting to play around with that idea. Feel free to implement something like that. sirjofri