eventlogd_selinux(8)
eventlogd_selinux π β the SELinux Policy eventlogd page, bestie edition
okay so this is eventlogd_selinux(8), the manual page for the SELinux policy that wrangles the eventlogd processes. it's from the SELinux Policy eventlogd collection and honestly? it's kind of iconic. let's get into it β¨
β¨ NAME β¨
eventlogd_selinux β Security Enhanced Linux Policy for the eventlogd processes. that's the whole vibe. she's a policy page and she knows it π
π¦ DESCRIPTION π¦
Security-Enhanced Linux secures the eventlogd processes via flexible mandatory access control. no cap, that's the actual job.
the eventlogd processes execute with the eventlogd_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 eventlogd_t
literally just run that and see what's up π
πΈ ENTRYPOINTS πΈ
the eventlogd_t SELinux type can be entered via the eventlogd_exec_t file type. that's the doorway, periodt.
the default entrypoint paths for the eventlogd_t domain are the following:
/usr/bin/eventlogd, /opt/likewise/sbin/eventlogd
those two paths, exactly, no more no less π«Ά
π PROCESS TYPES π
SELinux defines process types (domains) for each process running on the system. yes, every single one gets a little label. organized queen behavior.
you can see the context of a process using the -Z option to ps
Policy governs the access confined processes have to files. SELinux eventlogd policy is very flexible allowing users to setup their eventlogd processes in as secure a method as possible.
the following process types are defined for eventlogd:
eventlogd_t
Note:semanage permissive -a eventlogd_tcan be used to make the process typeeventlogd_tpermissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated.
so like, permissive means she won't block you, but she's still gonna write it down in her notes π the receipts stay.
π₯ BOOLEANS π₯
SELinux policy is customizable based on least access required. eventlogd policy is extremely flexible and has several booleans that allow you to manipulate the policy and run eventlogd with the tightest access possible. tightest access = main character security energy, iykyk.
- if you want to
dontauditall daemons scheduling requests (setsched,sys_nice), you must turn on thedaemons_dontaudit_schedulingboolean. 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 thefips_modeboolean. Enabled by default.
setsebool -P fips_mode 1
both of those are enabled by default btw, so if you're checking, they should already be slaying π
π§ MANAGED FILES π§
the SELinux process type eventlogd_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 said "i got the labels" but DAC said "i still need my perms" β they're a team π€)
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
eventlogd_var_lib_t
/var/lib/likewise/db/lwi_events.db
/var/lib/likewise-open/db/lwi_events.db
eventlogd_var_run_t
/run/eventlogd.pid
root_t
/sysroot/.aleph-version.json
/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd
/var/lib/ntp
look at all those paths, she's thorough π
π FILE CONTEXTS π
SELinux requires files to have an extended attribute to define the file type. it's giving "everything has a label, no exceptions."
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 eventlogd policy is very flexible allowing users to setup their eventlogd processes in as secure a method as possible.
β STANDARD FILE CONTEXT β
SELinux defines the file context types for the eventlogd, 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 eventlogd_exec_t '/srv/eventlogd/content(/.*)?'
restorecon -R -v /srv/myeventlogd_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 eventlogd:
π eventlogd_exec_t
- Set files with the
eventlogd_exec_ttype, if you want to transition an executable to theeventlogd_tdomain.
Paths:
/usr/bin/eventlogd, /opt/likewise/sbin/eventlogd
π eventlogd_var_lib_t
- Set files with the
eventlogd_var_lib_ttype, if you want to store theeventlogdfiles under the/var/libdirectory.
Paths:
/var/lib/likewise/db/lwi_events.db, /var/lib/likewise-
open/db/lwi_events.db
(that line break in /var/lib/likewise-open/db/lwi_events.db is literally in the original, we keep it fr fr)
π eventlogd_var_run_t
- Set files with the
eventlogd_var_run_ttype, if you want to store theeventlogdfiles under the/runor/var/rundirectory.
π eventlogd_var_socket_t
- Set files with the
eventlogd_var_socket_ttype, if you want to treat the files aseventlogdvar socket data.
Paths:
/var/lib/likewise/.eventlog, /var/lib/likewise/rpc/socket,
/var/lib/likewise-open/.eventlog, /var/lib/likewise-open/rpc/socket
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 π chcon is the quick fix, semanage fcontext + restorecon is the real glow-up.
π 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 booleanssystem-config-selinuxis a GUI tool available to customize SELinux policy settings.
all the tools, one little toolbelt π§°β¨
π AUTHOR π
This manual page was auto-generated using sepolicy manpage . β yes she was generated, and she still ate π
β SEE ALSO β
selinux(8), eventlogd(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8)
go read those next, the lore is deep π«Ά
and that's the page, bestie π this version dropped on 26-10-06 and the original footer called it eventlogd_selinux(8) β same energy, way more sparkle. you're welcome, now go label some files πβ¨
π¦ 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