FM / log

/var/log

Name	Size	Mode	Actions
anaconda/	-	0755	rm
apache2/	-	0711	rm
archive/	-	0700	rm
audit/	-	0700	rm
chrony/	-	0750	rm
cpanel-server-traffic/	-	0700	rm
dcpumon/	-	0700	rm
imunify360/	-	0700	rm
imunify360_user_logs/	-	1777	rm
named/	-	0755	rm
private/	-	0700	rm
qemu-ga/	-	0755	rm
sa/	-	0755	rm
samba/	-	0700	rm
sssd/	-	0750	rm
sw-cp-server/	-	0750	rm
btmp	5496192	0660	edit dl rm
btmp-20260901	42077952	0660	edit dl rm
chkservd.log	1513803	0600	edit dl rm
comet_backup_jobs_helper.log	0	0640	edit dl rm
cpanel-install.log	742937	0600	edit dl rm
cron	808318582	0600	edit dl rm
cron-20260816	7171641	0600	edit dl rm
cron-20260823	7181221	0600	edit dl rm
cron-20260830	7189213	0600	edit dl rm
cron-20260906	1142762574	0600	edit dl rm
dmesg	50828	0644	edit dl rm
dnf.librepo.log	245632	0644	edit dl rm
dnf.librepo.log.1	1048506	0644	edit dl rm
dnf.librepo.log.2	1048486	0644	edit dl rm
dnf.librepo.log.3	1048453	0644	edit dl rm
dnf.librepo.log.4	1048479	0644	edit dl rm
dnf.log	356342	0644	edit dl rm
dnf.log.1	1048540	0644	edit dl rm
dnf.log.2	1048542	0644	edit dl rm
dnf.log.3	1048541	0644	edit dl rm
dnf.log.4	1048535	0644	edit dl rm
dnf.rpm.log	470177	0644	edit dl rm
dnf.rpm.log.1	1048556	0644	edit dl rm
dnf.rpm.log.2	1048570	0644	edit dl rm
dpkg.log	0	0644	edit dl rm
exim_mainlog	40360089	0640	edit dl rm
exim_mainlog-20260816.gz	7897622	0640	edit dl rm
exim_mainlog-20260823.gz	6920093	0640	edit dl rm
exim_mainlog-20260830.gz	9094683	0640	edit dl rm
exim_mainlog-20260906.gz	13664963	0640	edit dl rm
exim_paniclog	0	0640	edit dl rm
exim_paniclog-20260816.gz	162	0640	edit dl rm
exim_paniclog-20260823.gz	20	0640	edit dl rm
exim_paniclog-20260830.gz	20	0640	edit dl rm
exim_paniclog-20260906.gz	20	0640	edit dl rm
exim_rejectlog	12265264	0640	edit dl rm
exim_rejectlog-20260816.gz	2305542	0640	edit dl rm
exim_rejectlog-20260823.gz	2002113	0640	edit dl rm
exim_rejectlog-20260830.gz	3053305	0640	edit dl rm
exim_rejectlog-20260906.gz	4828758	0640	edit dl rm
fail2ban.log	5151475	0600	edit dl rm
fail2ban.log-20260816	15329163	0600	edit dl rm
fail2ban.log-20260823	11134187	0600	edit dl rm
fail2ban.log-20260830	11384370	0600	edit dl rm
fail2ban.log-20260906	8243748	0600	edit dl rm
hawkey.log	19920	0644	edit dl rm
hawkey.log-20260816	29940	0644	edit dl rm
hawkey.log-20260823	29760	0644	edit dl rm
hawkey.log-20260830	30660	0644	edit dl rm
hawkey.log-20260906	30120	0644	edit dl rm
imav-deploy.log	37179	0600	edit dl rm
imunify-agent-proxy.log	435053	0644	edit dl rm
lastlog	303096	0664	edit dl rm
maillog	48165214	0600	edit dl rm
maillog-20260816	41556549	0600	edit dl rm
maillog-20260823	27779589	0600	edit dl rm
maillog-20260830	32006274	0600	edit dl rm
maillog-20260906	47381548	0600	edit dl rm
malware-watchdog.log	3931245	0644	edit dl rm
messages	472507946	0600	edit dl rm
messages-20260816	13835883	0600	edit dl rm
messages-20260823	13833537	0600	edit dl rm
messages-20260830	14116278	0600	edit dl rm
messages-20260906	667702367	0600	edit dl rm
mysqld.log	2569315	0640	edit dl rm
quota_enable.log	29826	0600	edit dl rm
README	1040	0644	edit dl rm
secure	21065952	0600	edit dl rm
secure-20260816	12254417	0600	edit dl rm
secure-20260823	10500493	0600	edit dl rm
secure-20260830	14491492	0600	edit dl rm
secure-20260906	28786893	0600	edit dl rm
spooler	0	0600	edit dl rm
spooler-20260816	0	0600	edit dl rm
spooler-20260823	0	0600	edit dl rm
spooler-20260830	0	0600	edit dl rm
spooler-20260906	0	0600	edit dl rm
tallylog	0	0600	edit dl rm
wp-toolkit	-	0	edit dl rm
wtmp	142080	0664	edit dl rm
xferlog.offsetftpsep	1	0644	edit dl rm

Edit: /usr/share/doc/systemd/README.logs (1040B)

You are looking for the traditional text log files in /var/log, and they are
gone?

Here's an explanation on what's going on:

You are running a systemd-based OS where traditional syslog has been replaced
with the Journal. The journal stores the same (and more) information as classic
syslog. To make use of the journal and access the collected log data simply
invoke "journalctl", which will output the logs in the identical text-based
format the syslog files in /var/log used to be. For further details, please
refer to journalctl(1).

Alternatively, consider installing one of the traditional syslog
implementations available for your distribution, which will generate the
classic log files for you. Syslog implementations such as syslog-ng or rsyslog
may be installed side-by-side with the journal and will continue to function
the way they always did.

Thank you!

Further reading:
        man:journalctl(1)
        man:systemd-journald.service(8)
        man:journald.conf(5)
        http://0pointer.de/blog/projects/the-journal.html

You are looking for the traditional text log files in /var/log, and they are gone? Here's an explanation on what's going on: You are running a systemd-based OS where traditional syslog has been replaced with the Journal. The journal stores the same (and more) information as classic syslog. To make use of the journal and access the collected log data simply invoke "journalctl", which will output the logs in the identical text-based format the syslog files in /var/log used to be. For further details, please refer to journalctl(1). Alternatively, consider installing one of the traditional syslog implementations available for your distribution, which will generate the classic log files for you. Syslog implementations such as syslog-ng or rsyslog may be installed side-by-side with the journal and will continue to function the way they always did. Thank you! Further reading: man:journalctl(1) man:systemd-journald.service(8) man:journald.conf(5) http://0pointer.de/blog/projects/the-journal.html