On 12/18/2014 05:48 PM, Zbigniew Jędrzejewski-Szmek wrote:
I think you should make it opt-in, with a command-line switch (--show-package
?).
In some cases it can be very useful, but most of the time it would
be just a slow down. If the switch is used, and packagekit does not
work, then this should cause a warning or an error though.
a) The name of the service is supposed to be descriptive enough
b) Encase it's not we already provide the ability to point to the
upstream documentation
c) This will slow down all containerized and virtualzation and
monitoring system that might be using the status ouput for one thing or
another
Bottom line what is the practical purpose of this since the
administrator is the one that a runs the status output on the service so
he's capable of a) determine the package by the name of the unit, gather
it from either the man page or the documentation link or by querying the
exact origin of the unit file using the package management installed on
his system?
What's the justification for the latency and the resource overhead to
provide this?
JBG
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
