<tt>Brandon Philips <brandon@ifup.co> wrote on 05/28/2015 05:10:33 PM: > Access to the system dbus is controlled by dbus policies. You will > need to write a policy for giving this user access to the systemd1 object.</tt> <tt>></tt> <tt>I compiled systemd without dbus support (--disable-dbus), and there is no dbus daemon or dbus lib on the system. Is that a requirement to get the functionality I want? I didn't see much need for dbus as the system works quite well without it. Well, except for this of course.</tt> <tt>> On May 28, 2015 2:28 PM, <Aaron_Wright@selinc.com> wrote:</tt> <tt>>> I'm working on an embedded system, and I ran into a situation where >> a non-root user needs to runs systemctl, but when I try I get: </tt> <tt>>> ~ $ systemctl status >> Failed to get D-Bus connection: No such file or directory >> >> So, I try with the suid bit on systemctl set, but then I get: >> >> ~ $ systemctl status >> Failed to read server status: Operation not permitted >> >> My question is, is something broken, or is this expected behavior?</tt>