From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] Re: feature request: log rotation
Date: Wed, 17 Feb 2021 09:59:36 -0500 [thread overview]
Message-ID: <2CC85240-8ADD-43FC-A6E3-73598A4D2EFC@stanleylieber.com> (raw)
In-Reply-To: <c7c04fa5-d120-497f-8b58-d3006f39ab58@sirjofri.de>
On February 17, 2021 2:45:55 AM EST, sirjofri <sirjofri+ml-9front@sirjofri.de> wrote:
>
>17.02.2021 00:34:17 Stanley Lieber <sl@stanleylieber.com>:
>> On February 15, 2021 11:53:42 PM EST, magma698hfsp273p9f@icebubble.org
>> wrote:
>>> Stanley Lieber <sl@stanleylieber.com> writes:
>>>
>>>> a machine sitting still should not fill up its own disk. let's design
>>>> a sane default.
>>>
>>> Isn't that the whole idea behind the WORM filesystem paradigm? Never
>>> delete anything, just add more storage. Right?
>>>
>>
>> i have seen many worms filled without human intervention. that's what
>> i'd like to prevent.
>>
>> i can roll my own log rotation, but why not provide a sensible default?
>>
>> note: not all systems have a worm partition or are running dumps. the
>> worm actually makes the problem worse.
>
>I thought dump only writes changed blocks, so if I don't write anything
>it doesn't fill the disk?
>
>(Log files set to temporary)
>
>sirjofri
>
a lot of programs write to files under /sys/log/.
files under /sys/log/ are not chmod +t by default.
sl
prev parent reply other threads:[~2021-02-17 15:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 15:36 [9front] " Stanley Lieber
2021-02-16 4:53 ` [9front] " magma698hfsp273p9f
2021-02-16 23:34 ` Stanley Lieber
2021-02-17 7:45 ` sirjofri
2021-02-17 14:59 ` Stanley Lieber [this message]
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=2CC85240-8ADD-43FC-A6E3-73598A4D2EFC@stanleylieber.com \
--to=sl@stanleylieber.com \
--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).