Summary: | dbus fails to start due to /run migration | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Amadeusz Sławiński <amade> |
Component: | SELinux | Assignee: | Sven Vermeulen (RETIRED) <swift> |
Status: | VERIFIED FIXED | ||
Severity: | normal | CC: | selinux |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | sec-policy r15 | ||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 424173 |
Description
Amadeusz Sławiński
2012-07-17 10:05:16 UTC
Is it the init script creating /run/dbus or the dbus daemon(s) itself? I'm assuming the init script (since the directory is currently labeled initrc_var_run_t) but it'd be nice if this can be confirmed. /var/run is link to /run from init script: # We need to test if /var/run/dbus exists, since script will fail if it does not [ ! -e /var/run/dbus ] && mkdir /var/run/dbus (In reply to comment #2) > /var/run is link to /run > > from init script: > > # We need to test if /var/run/dbus exists, since script will fail if it > does not > [ ! -e /var/run/dbus ] && mkdir /var/run/dbus tmpfs /run tmpfs mode=0755,nosuid,nodev,rootcontext=system_u:object_r:var_run_t 0 0 do you have something similar in /etc/fstab, I start in enforcing with dbus and udev without a single problem from either daemon. Yes I have the exact same line [ebuild R ] sys-apps/dbus-1.6.2 USE="X (selinux) -debug -doc -static-libs -systemd -test" 0 kB For me it always fails Is /var/run a symbolic link to /run and if so, did you do that yourself or was that created by Gentoo? My ~amd64 VMs don't have a symlink to /run... It is... it is... Will be fixed in rev15 r15 now in hardened-dev overlay In main tree, ~arched stabilized |