setroubl...d_selinux(8)
π setroubleshootd_selinux β like, the whole SELinux policy vibe for setroubleshootd processes (section 8, bestie)
Okay so this is the <pink>setroubleshootd_selinux</pink> manpage, and yes the title is literally abbreviated in the header because manpage titles are dramatic like that. Buckle up π
β¨ NAME β¨
setroubleshootd_selinux β the Security Enhanced Linux Policy for the setroubleshootd processes. That's it, that's the whole name, periodt π
πΈ DESCRIPTION πΈ
Security-Enhanced Linux secures the setroubleshootd processes via flexible mandatory access control. Yes, mandatory β not the vibe where you get to opt out, bestie π«Ά
The setroubleshootd processes execute with the setroubleshootd_t SELinux type. Wanna check if you've got these processes running? Just run the ps command with the -Z qualifier. So cute, so simple β¨
For example:
ps -eZ | grep setroubleshootd_t
π¦ ENTRYPOINTS π¦
The setroubleshootd_t SELinux type can be entered via the setroubleshootd_exec_t file type. That's the doorway, the portal, the main character entrance π«
The default entrypoint paths for the setroubleshootd_t domain are literally these two:
/usr/bin/setroubleshootd,
/usr/share/setroubleshoot/SetroubleshootPrivileged.py
π PROCESS TYPES π
SELinux defines process types (domains) for each process running on the system. Every process gets a little label, like a name tag at a party π
You can see the context of a process using the -Z option to ps. Lowkey the most useful flag, iykyk.
Policy governs the access confined processes have to files. The SELinux setroubleshootd policy is very flexible, allowing users to setup their setroubleshootd processes in as secure a method as possible. Flexible AND secure? She contains multitudes π
The following process types are defined for setroubleshootd:
setroubleshootd_t, setroubleshoot_fixit_t
Note, bestie:semanage permissive -a setroubleshootd_tcan be used to make the process typesetroubleshootd_tpermissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. So it's chill about access but still keeps receipts π
π BOOLEANS π
SELinux policy is customizable based on least access required. Fr fr, minimum access only. The setroubleshootd policy is extremely flexible and has several booleans that allow you to manipulate the policy and run setroubleshootd with the tightest access possible. Tightest access = the look, the aesthetic π
daemons_dontaudit_schedulingβ if you want todontauditall daemons scheduling requests (setsched,sys_nice), you must turn on this boolean. Enabled by default. So:
setsebool -P daemons_dontaudit_scheduling 1
fips_modeβ if you want to allow all domains to execute infips_mode, you must turn on this boolean. Enabled by default. Slay:
setsebool -P fips_mode 1
nis_enabledβ if you want to allow system to run with NIS, you must turn on this boolean. Disabled by default. Note the difference, bestie, this one starts OFF:
setsebool -P nis_enabled 1
π MANAGED FILES π
The SELinux process type setroubleshootd_t can manage files labeled with the following file types. The paths listed are the default paths for these file types. Keep in mind the processes UID still need to have DAC permissions β SELinux isn't doing all the work, she's just doing her part π
cluster_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
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
root_t
/sysroot/.aleph-version.json
/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd
/var/lib/ntp
security_t
/selinux
setroubleshoot_tmp_t
(no default paths listed β she exists, that's the whole vibe β¨)
setroubleshoot_tmpfs_t
(again, no default paths listed β iconic and mysterious π¦)
setroubleshoot_var_lib_t
/var/lib/setroubleshoot(/.*)?
setroubleshoot_var_log_t
/var/log/setroubleshoot(/.*)?
setroubleshoot_var_run_t
/run/setroubleshoot(/.*)?
π FILE CONTEXTS π
SELinux requires files to have an extended attribute to define the file type. Yes, every file needs its little label, like a designer tag on a handbag π
You can see the context of a file using the -Z option to ls. Same energy as ps -Z, just for files.
Policy governs the access confined processes have to these files. The SELinux setroubleshootd policy is very flexible, allowing users to setup their setroubleshootd processes in as secure a method as possible. We love a flexible icon π«Ά
β STANDARD FILE CONTEXT β
SELinux defines the file context types for the setroubleshootd. So if you wanted to store files with these types in different paths, you need to execute the semanage command to specify alternate labeling and then use restorecon to put the labels on disk. Like so:
semanage fcontext -a -t setroubleshootd_exec_t '/srv/setroubleshootd/content(/.*)?'
restorecon -R -v /srv/mysetroubleshootd_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. Regex era, honestly obsessed π
The following file types are defined for setroubleshootd:
setroubleshootd_exec_t
- Set files with the
setroubleshootd_exec_ttype, if you want to transition an executable to thesetroubleshootd_tdomain.
Paths:
/usr/bin/setroubleshootd,
/usr/share/setroubleshoot/SetroubleshootPrivileged.py
Note: File context can be temporarily modified with thechconcommand. But 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. So:chconfor a quick little moment,semanage fcontext+restoreconfor the forever thing. Don't mix them up bestie π
π COMMANDS π
semanage fcontextcan also be used to manipulate default file context mappings.semanage permissivecan also be used to manipulate whether or not a process type is permissive.semanage modulecan also be used to enable/disable/install/remove policy modules.semanage booleancan also be used to manipulate the booleans.system-config-selinuxis a GUI tool available to customize SELinux policy settings. For when you want buttons instead of typing, no judgment πΈ
π§ AUTHOR π§
This manual page was auto-generated using sepolicy manpage. Not a human author, a generator β she's giving automated main character energy π€β¨
π₯ SEE ALSO π₯
selinux(8), setroubleshootd(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8), setroubleshoot_fixit_selinux(8)
Okay that's the whole page bestie, go forth and label responsibly π This was setroubleshootd from the setroubl...d_selinux(8) manual, dated 26-10-06. Mwah, slay, periodt π
π¦ 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