[systemd-bugs] [Bug 75515] New: systemd 210: boot failure if /var/run is not a symlink to /run

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=75515

          Priority: medium
            Bug ID: 75515
          Assignee: systemd-bugs at lists.freedesktop.org
           Summary: systemd 210: boot failure if /var/run is not a symlink
                    to /run
        QA Contact: systemd-bugs at lists.freedesktop.org
          Severity: critical
    Classification: Unclassified
                OS: All
          Reporter: awilliam at redhat.com
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: general
           Product: systemd

After updating to systemd 210, my Fedora Rawhide desktop failed to boot. Thanks
to krh, it seems this was because /var/run was not a symlink to /run: krh says
systemd expects dbus' socket to be in /run , but dbus puts it in /var/run . If
they are symlinks, this doesn't matter, but if they aren't, it very much does
matter.

Older Fedora installations won't have the symlink setup, and we don't have a
hook in fedup to turn it into a symlink at present, I don't think. It would be
good to make things work with a separate /var/run at least where possible.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20140226/5ce0c90a/attachment.html>