On Di, 27.09.22 10:12, Chris Murphy (li...@colorremedies.com) wrote:
65;6800;1c
> The obvious bike-shedding questions are: Is 4G is too much or too
> little? If so what amount it should be? Is size still the correct
> approach? Or should we consider a max retention time? And if so,
> what would it
On Tue, Sep 27, 2022, at 7:14 PM, Allan via devel wrote:
> On Tue, 27 Sep 2022 12:31:11 -0600
> "Chris Murphy" wrote:
>
> The original PinePhone only comes with a 16GB eMMC. Using 4GB for
> journal on that would for sure be insane.
The root file system for this device might be around 15G,
devel
Subject: limiting the (systemd) journal size
!---|
This Message Is From an External Sender
|---!
Hi,
Fedora uses systemd-journald for system logging. By default
If the disk space was unlimited, I'd love to keep the journal forever.
Since I don't have unlimited storage, I prefer to be space limited
rather then time limited.
IOW the journal entries are typically useless even before they are
recorded, but when there is some troubleshooting required, the
On Tue, 27 Sep 2022 12:31:11 -0600
"Chris Murphy" wrote:
[..]
> >> The obvious bike-shedding questions are:
> >> Is 4G is too much or too little? If so what amount it should be?
> >> Is size still the correct approach? Or should we consider a max
> >> retention time? And if so, what would it be
Hi,
On September 27, 2022 6:13:48 PM UTC, Chris Murphy
wrote:
>
>
>On Tue, Sep 27, 2022, at 10:59 AM, Gregory Bartholomew wrote:
>>>
>>> What about modifying /etc/systemd/journald.conf:
>>>
>>> MaxFileSec=1week
>>> MaxRetentionSec=5week
>>>
>>> This should result in at least 4 weeks of
On Tue, Sep 27, 2022, at 12:13 PM, Daniel P. Berrangé wrote:
> On Tue, Sep 27, 2022 at 10:12:57AM -0600, Chris Murphy wrote:
>> Hi,
>>
>> Fedora uses systemd-journald for system logging. By default it is a
>> persistent log kept on /var, and uses up to 4G disk space, although
>> in certain
> On Tue, Sep 27, 2022, at 10:59 AM, Chris Murphy wrote:
>
> I hadn't considered the container case at all, that containers running
> systemd-journald would have their own journals and retention policy. I wonder
> if the
> container default should have volatile journals? Or forward the journals
On Tue, Sep 27, 2022, at 10:59 AM, Gregory Bartholomew wrote:
>>
>> What about modifying /etc/systemd/journald.conf:
>>
>> MaxFileSec=1week
>> MaxRetentionSec=5week
>>
>> This should result in at least 4 weeks of journal entries, i.e. it would
>> delete a journal
>> file once entries reach 5
On Tue, Sep 27, 2022 at 10:12:57AM -0600, Chris Murphy wrote:
> Hi,
>
> Fedora uses systemd-journald for system logging. By default it is a
> persistent log kept on /var, and uses up to 4G disk space, although
> in certain circumstances it can go a bit higher. See 'man journald.conf'
> for
>
> What about modifying /etc/systemd/journald.conf:
>
> MaxFileSec=1week
> MaxRetentionSec=5week
>
> This should result in at least 4 weeks of journal entries, i.e. it would
> delete a journal
> file once entries reach 5 weeks old, but since the journal files are rotated
> weekly, it
>
On Tue, Sep 27, 2022, at 10:38 AM, Gregory Bartholomew wrote:
> FWIW (probably not much), I have run into an issue with regard to the
> default journal size being too large on Fedora Server when running a
> bunch of systemd-nspawn containers each with sshd and fail2ban enabled.
> When I
FWIW (probably not much), I have run into an issue with regard to the default
journal size being too large on Fedora Server when running a bunch of
systemd-nspawn containers each with sshd and fail2ban enabled. When I reboot a
bunch of the containers at once (or the whole hypervisor), fail2ban
Hi,
Fedora uses systemd-journald for system logging. By default it is a persistent
log kept on /var, and uses up to 4G disk space, although in certain
circumstances it can go a bit higher. See 'man journald.conf' for details.
Example:
>Sep 27 07:26:05 fovo.local systemd-journald[602]: System
14 matches
Mail list logo
