systemd/man/user-system-options.xml
Tom Gundersen 12b42c7667 man: revert dynamic paths for split-usr setups
This did not really work out as we had hoped. Trying to do this upstream
introduced several problems that probably makes it better suited as a
downstream patch after all. At any rate, it is not releaseable in the
current state, so we at least need to revert this before the release.

 * by adjusting the path to binaries, but not do the same thing to the
   search path we end up with inconsistent man-pages. Adjusting the search
   path too would be quite messy, and it is not at all obvious that this is
   worth the effort, but at any rate it would have to be done before we
   could ship this.

 * this means that distributed man-pages does not make sense as they depend
   on config options, and for better or worse we are still distributing
   man pages, so that is something that definitely needs sorting out before
   we could ship with this patch.

 * we have long held that split-usr is only minimally supported in order
   to boot, and something we hope will eventually go away. So before we start
   adding even more magic/effort in order to make this work nicely, we should
   probably question if it makes sense at all.
2015-06-18 19:47:44 +02:00

51 lines
1.6 KiB
XML

<?xml version="1.0"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
<variablelist>
<varlistentry id='user'>
<term><option>--user</option></term>
<listitem id='user-text'>
<para>Talk to the service manager of the calling user,
rather than the service manager of the system.</para>
</listitem>
</varlistentry>
<varlistentry id='system'>
<term><option>--system</option></term>
<listitem id='system-text'>
<para>Talk to the service manager of the system. This is the
implied default.</para>
</listitem>
</varlistentry>
<varlistentry id='host'>
<term><option>-H</option></term>
<term><option>--host=</option></term>
<listitem id='host-text'>
<para>Execute the operation remotely. Specify a hostname, or a
username and hostname separated by <literal>@</literal>, to
connect to. The hostname may optionally be suffixed by a
container name, separated by <literal>:</literal>, which
connects directly to a specific container on the specified
host. This will use SSH to talk to the remote machine manager
instance. Container names may be enumerated with
<command>machinectl -H
<replaceable>HOST</replaceable></command>.</para>
</listitem>
</varlistentry>
<varlistentry id='machine'>
<term><option>-M</option></term>
<term><option>--machine=</option></term>
<listitem id='machine-text'>
<para>Execute operation on a local container. Specify a
container name to connect to.</para>
</listitem>
</varlistentry>
</variablelist>