fsdaemon_selinux(8)
π¦ fsdaemon_selinux β the whole vibe check on SELinux policy for fsdaemon π
okay so bestie, this is the manual page for fsdaemon_selinux, and it's literally all about the Security Enhanced Linux Policy for the fsdaemon processes. yes, the whole page. buckle up π
β¨ NAME β¨
fsdaemon_selinux β Security Enhanced Linux Policy for the fsdaemon processes. that's the whole name section, she's short and she knows it π
πΈ DESCRIPTION πΈ
so like, Security-Enhanced Linux secures the fsdaemon processes via flexible mandatory access control. that's the flex. no cap.
the fsdaemon processes execute with the fsdaemon_t SELinux type. and bestie, you can totally check if you have these processes running by executing the ps command with the -Z qualifier. here's the moment:
ps -eZ | grep fsdaemon_t
slay. that's it. that's the check π«Ά
πͺ ENTRYPOINTS πͺ
the fsdaemon_t SELinux type can be entered via the fsdaemon_exec_t file type. it's giving VIP entrance only π₯
the default entrypoint paths for the fsdaemon_t domain are literally just:
/usr/bin/smartd
one (1) path. iconic minimalism π
π PROCESS TYPES π
SELinux defines process types (domains) for each process running on the system. yes. every single one.
you can see the context of a process using the -Z option to ps. (we keep coming back to -Z, she's the main character here.)
Policy governs the access confined processes have to files. SELinux fsdaemon policy is very flexible, allowing users to setup their fsdaemon processes in as secure a method as possible. flexible AND secure? we love a multihyphenate π
the following process types are defined for fsdaemon:
fsdaemon_t
Note:semanage permissive -a fsdaemon_tcan be used to make the process typefsdaemon_tpermissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like, she's not gonna block you, but she WILL be watching and taking notes π
ποΈ BOOLEANS ποΈ
SELinux policy is customizable based on least access required. fsdaemon policy is extremely flexible and has several booleans that allow you to manipulate the policy and run fsdaemon with the tightest access possible. tightest access possible, bestie. we don't do sloppy here β¨
daemons_dontaudit_scheduling β 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
fips_mode β 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
nis_enabled β 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
smartmon_3ware β if you want to determine whether smartmon can support devices on 3ware controllers, you must turn on the smartmon_3ware boolean. disabled by default.
setsebool -P smartmon_3ware 1
virt_use_nfs β if you want to allow confined virtual guests to manage nfs files, you must turn on the virt_use_nfs boolean. disabled by default.
setsebool -P virt_use_nfs 1
virt_use_samba β if you want to allow confined virtual guests to manage cifs files, you must turn on the virt_use_samba boolean. disabled by default.
setsebool -P virt_use_samba 1
that's six booleans, all accounted for, no skips, we don't do that here π
π MANAGED FILES π
the SELinux process type fsdaemon_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 out here doing your whole job for you, she's just one layer of the cake π
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
fsdaemon_tmp_t
(no default paths listed here β she's mysterious like that π)
fsdaemon_var_lib_t
/var/lib/smartmontools(/.*)?
fsdaemon_var_run_t
/run/smartd.pid
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
mail_home_rw_t
/root/Maildir(/.*)?
/root/.esmtp_queue(/.*)?
/var/lib/arpwatch/.esmtp_queue(/.*)?
/var/cache/ddclient/.esmtp_queue(/.*)?
/home/[^/]+/.maildir(/.*)?
/home/[^/]+/Maildir(/.*)?
/home/[^/]+/.esmtp_queue(/.*)?
root_t
/sysroot/.aleph-version.json
/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd
/var/lib/ntp
security_t
/selinux
π·οΈ FILE CONTEXTS π·οΈ
SELinux requires files to have an extended attribute to define the file type. yes, files have vibes too and those vibes are stored as metadata π
you can see the context of a file using the -Z option to ls. (-Z again!! she's everywhere!! the range!!)
Policy governs the access confined processes have to these files. SELinux fsdaemon policy is very flexible allowing users to setup their fsdaemon processes in as secure a method as possible.
β STANDARD FILE CONTEXT β
SELinux defines the file context types for the fsdaemon. 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. like so:
semanage fcontext -a -t fsdaemon_exec_t '/srv/fsdaemon/content(/.*)?'
restorecon -R -v /srv/myfsdaemon_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regex girlies rise π
the following file types are defined for fsdaemon:
fsdaemon_exec_t
- Set files with the
fsdaemon_exec_ttype, if you want to transition an executable to thefsdaemon_tdomain.
fsdaemon_initrc_exec_t
- Set files with the
fsdaemon_initrc_exec_ttype, if you want to transition an executable to thefsdaemon_initrc_tdomain.
fsdaemon_tmp_t
- Set files with the
fsdaemon_tmp_ttype, if you want to storefsdaemontemporary files in the/tmpdirectories.
fsdaemon_var_lib_t
- Set files with the
fsdaemon_var_lib_ttype, if you want to store thefsdaemonfiles under the/var/libdirectory.
fsdaemon_var_run_t
- Set files with the
fsdaemon_var_run_ttype, if you want to store thefsdaemonfiles under the/runor/var/rundirectory.
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, bestie, know the difference ππ
π οΈ 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. (a GUI!! for the girlies who like clicking!! π)
ποΈ AUTHOR ποΈ
This manual page was auto-generated using sepolicy manpage. not me being a bot-written icon π€β¨
π SEE ALSO π
selinux(8), fsdaemon(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8)
and that's the whole page bestie, no notes, no skips, every path and every boolean intact π«Ά
sign-off time: this lil beauty lives in the fsdaemon manual, dated 26-10-06, and the page title she's filed under is fsdaemon_selinux(8). go forth and label responsibly ππ¦π
π¦ 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