man: clarify systemctl --property= documentation a bit

This commit is contained in:
Lennart Poettering 2013-02-28 19:55:48 +01:00
parent 3cd170c33e
commit 54c31a79f7
3 changed files with 10 additions and 8 deletions

1
.gitignore vendored
View File

@ -23,6 +23,7 @@
/systemadm
/systemctl
/systemd
/systemd-activate
/systemd-ac-power
/systemd-analyze
/systemd-ask-password

6
TODO
View File

@ -49,9 +49,11 @@ Fedora 19:
Features:
* systemd-inhibit: refuse taking delay locks
* journal-or-kmsg is currently broken? See reverted commit 4a01181e460686d8b4a543b1dfa7f77c9e3c5ab8.
* remove any syslog support from log.c
* remove any syslog support from log.c -- we probably can't do this before split-off udev is gone for good
* convert /etc/bash_completion.d/ to /usr/share/bash-completion/
(systemd (and everything else) should install zero static data in /etc)
@ -80,8 +82,6 @@ Features:
* man: maybe sort directives in man pages, and take sections from --help and apply them to man too
* man: systemctl: clarify that -p applies to "systemctl show" only
* add "# export SYSTEMD_PAGER=" to bash login
* /usr/bin/service should actually show the new command line

View File

@ -117,10 +117,11 @@ along with systemd; If not, see <http://www.gnu.org/licenses/>.
<term><option>--property=</option></term>
<listitem>
<para>When showing unit/job/manager properties, limit
display to certain properties as specified as argument. If
not specified all set properties are shown. The argument
should be a comma-seperated list of property names, such as
<para>When showing unit/job/manager properties with the
<command>show</command> command, limit display to certain
properties as specified as argument. If not specified all
set properties are shown. The argument should be a
comma-seperated list of property names, such as
<literal>MainPID</literal>. If specified more than once all
properties with the specified names are shown.</para>
</listitem>
@ -206,7 +207,7 @@ along with systemd; If not, see <http://www.gnu.org/licenses/>.
sleep state. Any user may take these locks and privileged
users may override these locks. If any locks are taken,
shutdown and sleep state requests will normally fail
(regardless if privileged or not) and list of active locks
(regardless if privileged or not) and a list of active locks
is printed. However if <option>--ignore-inhibitors</option>
is specified the locks are ignored and not printed, and the
operation attempted anyway, possibly requiring additional