On Tue, Nov 06, 2012 at 03:23:25AM +0800, Rashif Ray Rahman wrote: > On 6 November 2012 02:50, Squall Lionheart <headmastersquall@xxxxxxxxx> wrote: > >> > >> I guess running "systemctl" should tell you? If you are using systemd > >> it will list a lot of running services. Otherwise I assume it will > >> return a dbus error (but I haven't tried that myself, so only a > >> guess). > >> > >> > > FYI, I haven't updated to systemd yet and the error when running systemctl > > reads: > > Failed to get D-Bus connection: No connection to service manager. > > Yes, that is correct behaviour, and means you're not running systemd. > I believe a valid logind session needs to exist for these to work, and > that means booting with systemd. Just to be clear, the logind session isn't needed -- systemd's private socket needs to be available, meaning /run/systemd/private exists. d
