Re: too-nearly-full filesystem '/'. (was upgrade problem: space on '/' filesystem.)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 10/21/19 11:32 AM, home user wrote:
> The key to getting good answers is to ask good questions.
Apparently, I'm not quite asking "good questions" this weekend.

I was looking for a more integrated view of journald so I could differentiate the advice given in this thread, and see how the two approaches provided in this thread converge or diverge.  (Why do I feel like a mathematician right now?) None of the 4 sources:
the Fedora sys. admin. guide, the digitalocean tutorial, the journalctl man page, and the journald.conf man page
quite do it, separately or together.

For review, the two approaches are:
A. using journald.conf to customize journald, and
B. (1) "journalctl --flush --rotate"; (2) "rm -rfv /var/log/journal/*/*@*"; (3) "journalctl --update-catalog --sync".

My first question:
If I use journald.conf to, say (hypothetical values for now):
* have the system start a new journald file each day, and
* delete journald files once they're a month old,
would I still need to do B above, or will A automatically cause the clean-out of all journald files more than a month old (maybe the next day or after a reboot)?

Second question:
What is the preferred way of changing the journald configuration?  That is, is there some GUI or tool for that, or do I simply edit "/etc/systemd/journald.conf" using my favorite editor (vi)?

Third question:
My impression is that approach B is only a temporary fix; "/var/log/journal/" would eventually get huge again.  Am I correct?



It simply sounds as if you want to limit the disk space used by the journal.

Reading the man page you'd see:

           SystemMaxUse= and RuntimeMaxUse= control how much disk space the
           journal may use up at most.  SystemKeepFree= and RuntimeKeepFree=
           control how much disk space systemd-journald shall leave free for
           other uses.  systemd-journald will respect both limits and use the
           smaller of the two values.

           The first pair defaults to 10% and the second to 15% of the size of
           the respective file system, but each value is capped to 4G.

So, yes, the size would grow to 4G where it is capped.

To me, 4G isn't all that huge since I've got plenty of space available.

So, just adjust those parameters to something you're comfortable with.

And, yes, use vi to edit the file.



--
The key to getting good answers is to ask good questions.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux