From: sirjofri <sirjofri+ml-9front@sirjofri.de>
To: 9front@9front.org
Subject: Re: [9front] Re: [9front] Re: [9front] Dealing with log files…
Date: Mon, 18 Oct 2021 08:51:26 +0000 (UTC) [thread overview]
Message-ID: <029d4fad-b2fb-4d9b-a0e2-577574e6950c@sirjofri.de> (raw)
In-Reply-To: <28C9A8BDB0039016DE60A0FCC1FCBFAF@antares-labs.eu>
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
next prev parent reply other threads:[~2021-10-18 9:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-16 20:06 igor
2021-10-16 20:52 ` umbraticus
2021-10-16 21:01 ` [9front] " Stanley Lieber
2021-10-17 8:29 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2021-10-17 9:06 ` umbraticus
2021-10-17 10:30 ` igor
2021-10-17 14:19 ` [9front] " Stanley Lieber
2021-10-17 12:29 ` Rodrigo G. López
2021-10-17 13:50 ` [9front] " hiro
2021-10-18 7:03 ` rgl
2021-10-18 8:51 ` sirjofri [this message]
2021-10-18 18:49 ` Steve Simon
2021-10-18 19:40 ` cinap_lenrek
2021-10-17 18:15 ` smj
2021-10-18 7:35 ` [9front] " Silas McCroskey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=029d4fad-b2fb-4d9b-a0e2-577574e6950c@sirjofri.de \
--to=sirjofri+ml-9front@sirjofri.de \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).