shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-11-01 09:21:26 +03:00
Code
912f003fc3
systemd/man/user-system-options.xml

51 lines
1.6 KiB
XML
Raw Normal View History

man: xinclude --user/--system
2014-02-13 23:40:40 +04:00
<?xml version="1.0"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
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 20:47:44 +03:00
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
man: xinclude --user/--system
2014-02-13 23:40:40 +04:00
<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>
man: xinclude --host/--machine As usual, those common options are pushed to the end.
2014-02-21 04:47:03 +04:00
<varlistentry id='host'>
<term><option>-H</option></term>
<term><option>--host=</option></term>
<listitem id='host-text'>
man: document that systemctl's -H may now be used to connect directly to a container on a remote host
2014-07-03 22:37:10 +04:00
<para>Execute the operation remotely. Specify a hostname, or a
man: xinclude --host/--machine As usual, those common options are pushed to the end.
2014-02-21 04:47:03 +04:00
username and hostname separated by <literal>@</literal>, to
man: document that systemctl's -H may now be used to connect directly to a container on a remote host
2014-07-03 22:37:10 +04:00
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>
man: xinclude --host/--machine As usual, those common options are pushed to the end.
2014-02-21 04:47:03 +04:00
</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>
man: xinclude --user/--system
2014-02-13 23:40:40 +04:00
</variablelist>
Copy Permalink