shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2025-03-08 08:58:27 +03:00
Code

man: be more explicit about the usefulness of --system

Browse Source
This commit is contained in:
Lennart Poettering 2010-10-26 23:22:55 +02:00
parent cbe1bded5f
commit 248e6030e0
2 changed files with 10 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
TODO
View File

@ -1,5 +1,3 @@
* man: clarify that --system works only for pid == 1
* oneshot services which do not remain: 'exited' instead of 'dead'? * oneshot services which do not remain: 'exited' instead of 'dead'?
it should be visible in 'systemctl' that they have been run it should be visible in 'systemctl' that they have been run

14
man/systemd.xml
View File

@ -141,14 +141,20 @@
<listitem><para>Tell systemd to run a <listitem><para>Tell systemd to run a
system instance (resp. session system instance (resp. session
instance), even if the process ID is instance), even if the process ID is
not 1 (resp. is 1), i.e. systemd is not not 1 (resp. is 1), i.e. systemd is
(resp. is) run as init process. not (resp. is) run as init process.
Normally it should not be necessary to Normally it should not be necessary to
pass these options, as systemd pass these options, as systemd
automatically detects the mode it is automatically detects the mode it is
started in. These options are hence of started in. These options are hence of
little use except for little use except for debugging. Note
debugging.</para></listitem> that it is not supported booting and
maintaining a full system with systemd
running in <option>--system</option>
mode, but PID not 1. In practice,
passing <option>--system</option> explicitly is
only useful in conjunction with
<option>--test</option>.</para></listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
<term><option>--dump-core</option></term> <term><option>--dump-core</option></term>