system...elinux(8)
π
systemd_rc_local_generator_selinux β the SELinux policy page for systemd_rc_local_generator
okay bestie, welcome to the system...elinux(8) manual page, this one's all about keeping the systemd_rc_local_generator processes on a leash (a cute, mandatory-access-control leash). it's giving security, it's giving structure, it's giving "your fave generator has a whole domain to itself." let's get into it π
β¨ NAME β¨
systemd_rc_local_generator_selinux β Security Enhanced Linux Policy for the systemd_rc_local_generator processes π¦
πΈ DESCRIPTION πΈ
Security-Enhanced Linux secures the systemd_rc_local_generator processes via flexible mandatory access control. no cap, that's the whole vibe.
The systemd_rc_local_generator processes execute with the systemd_rc_local_generator_t SELinux type. want to check if you've got these processes running? just run the ps command with the -Z qualifier, like so:
ps -eZ | grep systemd_rc_local_generator_t
look at you, doing a vibe check on your processes. iconic π
πͺ ENTRYPOINTS πͺ
The systemd_rc_local_generator_t SELinux type can be entered via the systemd_rc_local_generator_exec_t file type. that's the door, that's the entrance, that's the moment the main character walks in β¨
The default entrypoint paths for the systemd_rc_local_generator_t domain are literally these:
/usr/lib/systemd/system-generators/systemd-rc-local-generator
π― PROCESS TYPES π―
SELinux defines process types (domains) for each process running on the system. yes, every process gets its own little domain. main character energy for everyone, honestly.
You can see the context of a process using the -Z option to ps. (yes, -Z again. it's the it-girl flag of this whole page π
)
Policy governs the access confined processes have to files. The SELinux systemd_rc_local_generator policy is very flexible, allowing users to setup their systemd_rc_local_generator processes in as secure a method as possible. flexible AND secure? we love a duality π
The following process types are defined for systemd_rc_local_generator:
systemd_rc_local_generator_t
Note:semanage permissive -a systemd_rc_local_generator_tcan be used to make the process typesystemd_rc_local_generator_tpermissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so it's chill about the denying, but it's still gonna talk about it. messy but valid π
ποΈ BOOLEANS ποΈ
SELinux policy is customizable based on least access required. the systemd_rc_local_generator policy is extremely flexible and has several booleans that allow you to manipulate the policy and run systemd_rc_local_generator with the tightest access possible. toggle girlies, this is your moment π
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
π MANAGED FILES π
The SELinux process type systemd_rc_local_generator_t can manage files labeled with the following file types. The paths listed are the default paths for these file types. quick lil reminder tho: the processes UID still need to have DAC permissions. SELinux isn't out here overriding the classics, bestie π«Ά
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
root_t
/sysroot/.aleph-version.json
/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd
/var/lib/ntp
π·οΈ FILE CONTEXTS π·οΈ
SELinux requires files to have an extended attribute to define the file type. it's like a name tag but for files, and the bouncer actually checks it π₯
You can see the context of a file using the -Z option to ls. told you -Z was that girl π
Policy governs the access confined processes have to these files. The SELinux systemd_rc_local_generator policy is very flexible, allowing users to setup their systemd_rc_local_generator processes in as secure a method as possible.
π STANDARD FILE CONTEXT π
SELinux defines the file context types for the systemd_rc_local_generator. 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 moving into a new place and actually hanging up the labels instead of leaving the boxes in the hallway, we're not doing that anymore π
semanage fcontext -a -t systemd_rc_local_generator_exec_t '/srv/systemd_rc_local_generator/content(/.*)?'
restorecon -R -v /srv/mysystemd_rc_local_generator_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regexes! she's flexible! she's matching multiple files at once! periodt π
The following file types are defined for systemd_rc_local_generator:
systemd_rc_local_generator_exec_t
- Set files with the
systemd_rc_local_generator_exec_ttype, if you want to transition an executable to thesystemd_rc_local_generator_tdomain.
systemd_rc_local_generator_unit_file_t
- Set files with the
systemd_rc_local_generator_unit_file_ttype, if you want to treat the files as systemd rc local generator unit content.
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. so like...chconis the temporary tattoo andsemanage fcontext+restoreconis the real one you commit to. choose wisely bestie π
π οΈ COMMANDS π οΈ
<yellow>semanage fcontext</yellow> can also be used to manipulate default file context mappings.
<yellow>semanage permissive</yellow> can also be used to manipulate whether or not a process type is permissive.
<yellow>semanage module</yellow> can also be used to enable/disable/install/remove policy modules.
<yellow>semanage boolean</yellow> 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 prefer clicking to typing π
π AUTHOR π
This manual page was auto-generated using sepolicy manpage. a bot wrote this and honestly? it ate β¨
π SEE ALSO π
selinux(8), systemd_rc_local_generator(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8)
π«Ά that's the whole page bestie!systemd_rc_local_generator,26-10-06, and yeah β this wassystem...elinux(8), the SELinux manual for thesystemd_rc_local_generatorpolicy. go forth, label things correctly, and slay π
π¦ 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