Reindl Harald wrote on 06/09/14 00:59: > > Am 05.09.2014 um 19:30 schrieb Mantas Mikulėnas: >> On Fri, Sep 5, 2014 at 8:22 PM, Jakub Klinkovský <j....@gmx.com> wrote: >>> >>> What is the reason behind logging unit's description? Consider the following >>> journal message (from `journalctl -b`): >>> >>> systemd[1]: Starting A secure, fast, compliant and very flexible >>> web-server... >>> >>> It shows some fancy stuff about the started unit, but does not point to any >>> particular unit as the description is ambiguous at best. >> >> It is somewhat expected that Description= will just have a >> more-readable version of the program's name, rather than some useless >> marketing. (Arch has "Apache Web Server" in its httpd.service.) I >> guess the service name also wasn't added because it'd make some lines >> really long, and because the journal can be queried for it anyway (-o >> verbose, etc) > > that don't change the fact that a desription is just a description > and systemd lacks a name value - logging like "starting start stops > whatever service" and "staretd start stops whatever service" is odd
I would argue that a Description= line which says "start stops whatever service" is a really bad description anyway. Surely "Description=Whatever" would make more sense here? And yes, this is just the message output. With -o verbose you can see the actual unit name anyway, so I'd say it's better he way it is now IMO. Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/ _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel