How many instances of "t" are there in:
Q: httpd acess_log doesn't always rotate I checked my logrotate configuration and it seems normal.  The logs do rotate, but once in a while an access_log is missed and it ends up becoming a file like: access_log-2022524 and it becomes huge like 500 MB on disk, on a computer I wasn't originally involved in setting up that has a whopping 7.6G in / total.   My current solution is writing a script that checks daily for the largest file over x amount that has the name access_log in it, nukes the file and restarts httpd to get rid of the file handle on it and recover the space.   I am not sure why some logs escape the rotate though.  As there is most definitely access log files that end in .gz so some are getting rotated ?  Just not always and unless here I find a more elegant solution I am going with the script that finds the large access_log file (which is random which date will be the winner) and removes it restarting apache too.
/etc/logrotate.conf:
# see "man logrotate" for details
# rotate log files weekly
weekly

# keep 4 weeks worth of backlogs
rotate 4

# create new (empty) log files after rotating old ones
create

# use date as a suffix of the rotated file
dateext

# uncomment this if you want your log files compressed
compress
compresscmd /usr/bin/xz
compressoptions '-9'

# RPM packages drop log rotation information into this directory
include /etc/logrotate.d

# no packages own wtmp and btmp -- we'll rotate them here
/var/log/wtmp {
  monthly
    create 0664 root utmp
    minsize 1M
    rotate 1
}

/var/log/btmp {
    missingok
    monthly
    create 0600 root utmp
    rotate 1
}

# system-specific logs may be also be configured here.

/etc/logrotate.d/httpd:
/var/log/httpd/*log {
    missingok
    notifempty
    sharedscripts
    delaycompress
    postrotate
        /bin/systemctl reload httpd.service > /dev/null 2>/dev/null || true
    endscript
}


user
The given text has 151 "t"s.
assistant