logrotate_selinux(8)
π logrotate_selinux β the manual page, but make it make sense
okay so bestie, welcome to logrotate_selinux(8), aka the SELinux policy page for all the logrotate processes. this is the logrotate entry in the SELinux Policy section of the manual, and it's genuinely iconic once you know how to read it. let's go π
β¨ NAME β¨
logrotate_selinux β Security Enhanced Linux Policy for the logrotate processes. periodt π
πΈ DESCRIPTION πΈ
Security-Enhanced Linux secures the logrotate processes via flexible mandatory access control. like, that's the whole vibe β SELinux is the bouncer and it checks everybody's label at the door π¦
The logrotate processes execute with the logrotate_t SELinux type. you can check if you have these processes running by executing the ps command with the -Z qualifier.
for example:
ps -eZ | grep logrotate_t
run it, see what shows up, it's giving detective energy π
πͺ ENTRYPOINTS πͺ
The logrotate_t SELinux type can be entered via the logrotate_exec_t file type. that's the doorway, that's the portal, that's how you get in β¨
The default entrypoint paths for the logrotate_t domain are the following:
/etc/cron.(daily|weekly)/sysklogd, /usr/bin/logrotate
π PROCESS TYPES π
SELinux defines process types (domains) for each process running on the system. yes, every single one, no cap.
You can see the context of a process using the -Z option to ps.
Policy governs the access confined processes have to files. SELinux logrotate policy is very flexible allowing users to setup their logrotate processes in as secure a method as possible. flexible and secure, we love a multitasker π
The following process types are defined for logrotate:
logrotate_t, logrotate_mail_t
Note:semanage permissive -a logrotate_tcan be used to make the process typelogrotate_tpermissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so it's not a free pass, it's just a "we're still watching, we're just not blocking" situation π
π BOOLEANS π
SELinux policy is customizable based on least access required. logrotate policy is extremely flexible and has several booleans that allow you to manipulate the policy and run logrotate with the tightest access possible. toggle toggles, bestie, that's the whole game π₯
If you want to allow logrotate to read logs inside, you must turn on the logrotate_read_inside_containers boolean. Disabled by default.
setsebool -P logrotate_read_inside_containers 1
If you want to allow logrotate to manage cifs files, you must turn on the logrotate_use_cifs boolean. Disabled by default.
setsebool -P logrotate_use_cifs 1
If you want to allow logrotate domain to manage fuse files, you must turn on the logrotate_use_fusefs boolean. Disabled by default.
setsebool -P logrotate_use_fusefs 1
If you want to allow logrotate to manage nfs files, you must turn on the logrotate_use_nfs boolean. Disabled by default.
setsebool -P logrotate_use_nfs 1
If you want to dontaudit all daemons scheduling requests (setsched, sys_nice), you must turn on the daemons_dontaudit_scheduling boolean. Enabled by default.
setsebool -P daemons_dontaudit_scheduling 1
If you want to allow all domains to execute in fips_mode, you must turn on the fips_mode boolean. Enabled by default.
setsebool -P fips_mode 1
If you want to allow system to run with NIS, you must turn on the nis_enabled boolean. Disabled by default.
setsebool -P nis_enabled 1
If you want to support NFS home directories, you must turn on the use_nfs_home_dirs boolean. Enabled by default.
setsebool -P use_nfs_home_dirs 1
If you want to support SAMBA home directories, you must turn on the use_samba_home_dirs boolean. Disabled by default.
setsebool -P use_samba_home_dirs 1
ποΈ MANAGED FILES ποΈ
The SELinux process type logrotate_t can manage files labeled with the following file types. The paths listed are the default paths for these file types. note β the processes UID still need to have DAC permissions. SELinux isn't gonna override good old-fashioned permissions, it's a stack, not a replacement π«Ά
abrt_var_cache_t
/var/tmp/abrt(/.*)?
/var/cache/abrt(/.*)?
/var/spool/abrt(/.*)?
/var/spool/debug(/.*)?
/var/cache/abrt-di(/.*)?
/var/spool/rhsm/debug(/.*)?
cifs_tcluster_conf_t
/etc/cluster(/.*)?
cluster_var_lib_t
/var/lib/pcsd(/.*)?
/var/lib/cluster(/.*)?
/var/lib/openais(/.*)?
/var/lib/pengine(/.*)?
/var/lib/corosync(/.*)?
/usr/lib/heartbeat(/.*)?
/var/lib/heartbeat(/.*)?
/var/lib/pacemaker(/.*)?
cluster_var_run_t
/run/crm(/.*)?
/run/cman_.*
/run/rsctmp(/.*)?
/run/aisexec.*
/run/heartbeat(/.*)?
/run/pcsd-ruby.socket
/run/corosync-qnetd(/.*)?
/run/corosync-qdevice(/.*)?
/run/pcsd.socket
/run/corosync.pid
/run/cpglockd.pid
/run/rgmanager.pid
/run/cluster/rgmanager.sk
collectd_rw_content_tfusefs_t
/run/user/[0-9]+/gvfs
krb5_host_rcache_t
/var/tmp/krb5_0.rcache2
/var/cache/krb5rcache(/.*)?
/var/tmp/nfs_0
/var/tmp/DNS_25
/var/tmp/host_0
/var/tmp/imap_0
/var/tmp/HTTP_23
/var/tmp/HTTP_48
/var/tmp/ldap_55
/var/tmp/ldap_487
/var/tmp/ldapmap1_0
logfileβ all log files π every single onelogrotate_lock_tlogrotate_tmp_tlogrotate_var_lib_t
/var/lib/logrotate(/.*)?
/var/lib/logrotate.status.*
named_cache_t
/var/lib/softhsm(/.*)?
/var/lib/unbound(/.*)?
/var/lib/named/data(/.*)?
/var/lib/named/slaves(/.*)?
/var/lib/named/dynamic(/.*)?
/var/lib/named/chroot/var/tmp(/.*)?
/var/lib/named/chroot/var/named/data(/.*)?
/var/lib/named/chroot/var/named/slaves(/.*)?
/var/lib/named/chroot/var/named/dynamic(/.*)?
nfs_topenshift_var_lib_t
/var/lib/openshift(/.*)?
/var/lib/stickshift(/.*)?
/var/lib/containers/home(/.*)?
root_t
/sysroot/.aleph-version.json
/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd
/var/lib/ntp
slrnpull_spool_t
/var/spool/slrnpull(/.*)?
var_lib_t
/opt/(.*/)?var/lib(/.*)?
/var/lib(/.*)?
/var/lib/ntp/var/lib(/.*)?
virt_cache_t
/var/cache/oz(/.*)?
/var/cache/libvirt(/.*)?
π·οΈ FILE CONTEXTS π·οΈ
SELinux requires files to have an extended attribute to define the file type. yes, required, not optional, this is not a suggestion babe π
You can see the context of a file using the -Z option to ls.
Policy governs the access confined processes have to these files. SELinux logrotate policy is very flexible allowing users to setup their logrotate processes in as secure a method as possible.
π EQUIVALENCE DIRECTORIES π
logrotate policy stores data with multiple different file context types under the /var/lib/logrotate directory. If you would like to store the data in a different directory you can use the semanage command to create an equivalence mapping. If you wanted to store this data under the /srv directory you would execute the following command:
semanage fcontext -a -e /var/lib/logrotate /srv/logrotate
restorecon -R -v /srv/logrotate
see, mapping made easy, slay β¨
π STANDARD FILE CONTEXT π
SELinux defines the file context types for the logrotate, if you wanted to store files with these types in a different paths, you need to execute the semanage command to specify alternate labeling and then use restorecon to put the labels on disk.
semanage fcontext -a -t logrotate_exec_t '/srv/logrotate/content(/.*)?'
restorecon -R -v /srv/mylogrotate_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regex girlies stay winning π
The following file types are defined for logrotate:
logrotate_exec_tβ Set files with thelogrotate_exec_ttype, if you want to transition an executable to thelogrotate_tdomain.
Paths:
/etc/cron.(daily|weekly)/sysklogd, /usr/bin/logrotate
logrotate_lock_tβ Set files with thelogrotate_lock_ttype, if you want to treat the files as logrotate lock data, stored under the/var/lockdirectorylogrotate_mail_tmp_tβ Set files with thelogrotate_mail_tmp_ttype, if you want to store logrotate mail temporary files in the/tmpdirectories.logrotate_tmp_tβ Set files with thelogrotate_tmp_ttype, if you want to store logrotate temporary files in the/tmpdirectories.logrotate_var_lib_tβ Set files with thelogrotate_var_lib_ttype, if you want to store the logrotate files under the/var/libdirectory.
Paths:
/var/lib/logrotate(/.*)?, /var/lib/logrotate.status.*
Note: File context can be temporarily modified with thechconcommand. If you want to permanently change the file context you need to use thesemanage fcontextcommand. This will modify the SELinux labeling database. You will need to userestoreconto apply the labels. temporary vs permanent, know the difference bestie π«Ά
π οΈ COMMANDS π οΈ
semanage fcontext can also be used to manipulate default file context mappings.
semanage permissive can also be used to manipulate whether or not a process type is permissive.
semanage module can also be used to enable/disable/install/remove policy modules.
semanage boolean can also be used to manipulate the booleans
system-config-selinux is a GUI tool available to customize SELinux policy settings. a whole GUI, for the girlies who like buttons π
βοΈ AUTHOR βοΈ
This manual page was auto-generated using sepolicy manpage. not me being a robot-authored icon π€π
π SEE ALSO π
selinux(8), logrotate(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8), logrotate_mail_selinux(8), logrotate_mail_selinux(8)
(yes, logrotate_mail_selinux(8) is listed twice in the original, and we are not erasing her, she said it twice for emphasis π)
okay that's the whole page bestie, go forth and label things π¦
sign-off: this waslogrotate_selinux(8), versionlogrotate, dated26-10-06. mwah π go check your booleans, ily, bye π
π¦ where this page comes from
- opensuse-leap 16.0: selinux-policy-doc 20250627+git412.dbf877ab7-160000.1.1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms