[systemd-bugs] [Bug 86415] systemd logs useless "mystery" warnings to the journal - log message fails to reference the source.

[bugzilla-daemon at freedesktop.org]

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

--- Comment #2 from James <james at nurealm.net> ---
Ok, I found the source of these, with a little help from someone having a
better grasp of systemd.  Silly me - I was looking for a reference from within
the unit files, rather than a reference from the systemd/system/ directories. 
The messages are generated from left-over links in
/etc/systemd/system/{multi-user.target.wants/cups.path,
printer.target.wants/cups.service, sockets.target.wants/cups.socket} to
non-existent unit files in /usr/lib/systemd/system/.

So, is there some way, in this case, to have an explicit reference back to the
broken link?  Something like:

 From /etc/systemd/system/sockets.target.wants/cups.socket - Cannot add
dependency job for unit cups.socket, ignoring: Unit cups.socket failed to load:
No such file or directory.

and

 From /etc/systemd/system/printer.target.wants/cups.service - Cannot add
dependency job for unit cups.service, ignoring: Invalid argument

Or - perhaps systemd could be a little smarter about not following broken
links.  The log message could then say something more direct, like:

 /etc/systemd/system/printer.target.wants/cups.service: No such file or
directory.

-- 
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/20141118/a300f122/attachment.html>