On 10 May 2011 22:26, Daniel Drake <[email protected]> wrote: > If I log the error after it tries to connect to /run/systemd/private, I get: > Failed to connect to socket /run/systemd/private: No such file or directory > > Indeed, there's nothing at that path, and the only thing in > /run/systemd/ is an empty directory at /run/systemd/ask-password
For completeness, this is a conflict between systemd and Fedora's readonly-root system. Filed at https://bugzilla.redhat.com/show_bug.cgi?id=704783 Now systemd is a bit happier :) Daniel _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
