The folder /var/log grows to upto 500 GB

acaciaorison · 06-26-2019, 09:04 AM

1-The installation of Grub script that generates config under .etc.default is missing apostrophe in sed ' s/slackware/slackware 14.2+ command that is in grub .
2-The the folder /var/log grows until the disk is full it reaches 500GB roughly. I attached the processes that are active in the attached file.
just today the result of du -f /var/log does not give correct size in GB usually it more than 100GB
-The Gimp 2.10 has no colors in toggle options and their black and grey and you hardly see them.in 2.8 version the pallet of all graphics tools is colored but in 2.10 it is grey.

-I tried slackware-current-install 64 bit and and slackware-install

frankbell · 06-26-2019, 07:30 PM

Do you have logrotate installed and configured?

In my experience, it is included with Slackware. This is from my Slackware box:

Code:

# whereis logrotate
logrotate: /usr/sbin/logrotate /etc/logrotate.d /etc/logrotate.conf /usr/man/man8/logrotate.8.gz

ponce · 06-27-2019, 02:03 AM

Welcome to LQ, acaciaorison!

Quote:

Originally Posted by acaciaorison

2-The the folder /var/log grows until the disk is full it reaches 500GB roughly. I attached the processes that are active in the attached file.
just today the result of du -f /var/log does not give correct size in GB usually it more than 100GB

what is the output of the command (as root)

Code:

du -a -x /var/log/ | sort -n | tail -30

Quote:

Originally Posted by acaciaorison

-The Gimp 2.10 has no colors in toggle options and their black and grey and you hardly see them.in 2.8 version the pallet of all graphics tools is colored but in 2.10 it is grey.

from the gimp menus: "Edit" -> "Preferences" -> "Interface" -> "Theme" -> "System".

allend · 06-27-2019, 09:50 AM

If you do not leave your computer on all the time, then the scripts in /etc/cron.daily/ likely will not run if you do not change the default 4:40am time in root's crontab.
My habit after an upgrade is to log in as root, cd to /etc/cron.daily/ and run the scripts manually. (With tab completion then typing ./c[Tab];./l[Tab];./ma[Tab];./ml[Tab][Enter] works.)
This will check certificates, do log rotation as well as update the man and mlocate databases.

100GB seems excessive, so the cause should be investigated, but I recently had to clear > 120GB out of the Windows\Temp directory on a Windows 7 machine after I found it had been bitten by a well known bug.