systemd-analyze critical chain some wrong...
Code:
# systemd-analyze critical-chain someone versed on Arch and systemd can look that? tia! |
It could be that your systemd log files are huge; check the size of /var/log/journal
You can limit log size by modifying /etc/systemd/journald.conf https://wiki.archlinux.org/index.php...nal_size_limit See man journald.conf |
1 Attachment(s)
Dude...is this 'normal' ?
just 2 files on /var/log/journal ?? |
Quote:
They are folders -- the logs are in the one named with a long alphanumeric string. How big is the folder on the left? Mine is 123.7MiB ATM. If yours is several GiB then that's why systemd is taking so long to boot -- delete the contents (if you have no outstanding issues on your system) and modify your /etc/systemd/journald.conf to limit the size as set out in my link above and described more fully in man journald.conf |
Quote:
I'd like to erase that folder... |
Quote:
Make sure your system is functioning properly first though... |
1 Attachment(s)
sorry 4 botherin u...
can I erase all of that? tia! |
Yes I'm pretty sure it will all be re-created by systemd; just move them to a different location if you're worried -- you can always just move them back if there's a problem.
|
All times are GMT -5. The time now is 06:52 PM. |