From 4ba2cd0d70d82629949f9d604685cd1f80c67f4a Mon Sep 17 00:00:00 2001 From: Daniel Hilst <392820+dhilst@users.noreply.github.com> Date: Wed, 21 Oct 2026 16:50:52 -0300 Subject: [PATCH] docs(selinux): the page says the daemon context is always in /opt/xcat The page states that the context belongs to the file in /opt/xcat. The prefix is now recorded at install time, so a relocated package starts the daemon of its own tree, and the file contexts still name /opt/xcat. Say both, so a reader of a relocated installation knows the entrypoints need their own entries. Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com> --- docs/source/advanced/selinux/index.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/source/advanced/selinux/index.rst b/docs/source/advanced/selinux/index.rst index 5dd7abadc8..fb935e3a57 100644 --- a/docs/source/advanced/selinux/index.rst +++ b/docs/source/advanced/selinux/index.rst @@ -64,6 +64,12 @@ unit must name ``xcatd`` and not a shell. 115 command names are symlinks to file it points to. ``/usr/sbin/xcatd`` is a symlink, and ``execve`` resolves it, so the context belongs to the file in ``/opt/xcat``. +The unit holds ``/opt/xcat`` as the default prefix, and ``%post`` writes +``/etc/xcat/xcatroot.env`` with the prefix of the installation, which the unit +reads after that default. The file contexts name ``/opt/xcat``, so a package +relocated with ``rpm --prefix`` starts in its own tree but needs its own file +context entries before the entrypoints reach ``xcat_t``. + Read the domain of the running daemon with:: ps -o label= -p "$(cat /run/xcatd.pid)"