[systemd-bugs] [Bug 51386] New: Broken symlinks in /lib/systemd/system partially breaks systemctl unit listing

[bugzilla-daemon at freedesktop.org]

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

             Bug #: 51386
           Summary: Broken symlinks in /lib/systemd/system partially
                    breaks systemctl unit listing
    Classification: Unclassified
           Product: systemd
           Version: unspecified
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: general
        AssignedTo: systemd-bugs at lists.freedesktop.org
        ReportedBy: zorael at gmail.com
         QAContact: systemd-bugs at lists.freedesktop.org


Kubuntu 12.04 x86_64, running systemd (185) git revision eab367b9 (120622).

If you have a broken symlink in /{,usr}/lib/systemd/system/ you can no longer
run 'systemctl list-unit-files', nor 'systemctl list-units --type=x' where x is
the file extension of your broken symlink. The error message is the very
generic 'file not found' message.

How to reproduce:
>$ sudo ln -sf asdf /lib/systemd/system/kittens.service
>$ systemctl list-unit-files
>Failed to issue method call: No such file or directory

The root cause here is user error (mine), obviously.

Could systemctl be tweaked to handle the situation more gracefully, or at the
very least mention what files it fails to read? Perhaps both?

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.
You are the assignee for the bug.