diff options
3 files changed, 16 insertions, 15 deletions
diff --git a/nixos/doc/manual/administration/rebooting.chapter.md b/nixos/doc/manual/administration/rebooting.chapter.md index 7a16a3a4ce5c3..ec4b889b1648c 100644 --- a/nixos/doc/manual/administration/rebooting.chapter.md +++ b/nixos/doc/manual/administration/rebooting.chapter.md @@ -22,9 +22,8 @@ directly loading the new kernel into memory: # systemctl kexec ``` -The machine can be suspended to RAM (if supported) using `systemctl - suspend`, and suspended to disk using `systemctl - hibernate`. +The machine can be suspended to RAM (if supported) using `systemctl suspend`, +and suspended to disk using `systemctl hibernate`. These commands can be run by any user who is logged in locally, i.e. on a virtual console or in X11; otherwise, the user is asked for diff --git a/nixos/doc/manual/administration/service-mgmt.chapter.md b/nixos/doc/manual/administration/service-mgmt.chapter.md index ba5c4cf15d545..ccf61c929ed1b 100644 --- a/nixos/doc/manual/administration/service-mgmt.chapter.md +++ b/nixos/doc/manual/administration/service-mgmt.chapter.md @@ -20,7 +20,7 @@ systemd as init system. NixOS is of no exception. The [next section ](#sect-nixos-systemd-nixos) explains NixOS specific things worth knowing. -Without any arguments, `systmctl` the status of active units: +Without any arguments, `systemctl` the status of active units: ```ShellSession $ systemctl @@ -96,12 +96,13 @@ the service on boot. *User* systemd services on the other hand, should be treated differently. Given a package that has a systemd unit file at -`#pkg-out#/lib/systemd/user/`, using [](#opt-systemd.packages) will +`#pkg-out#/lib/systemd/user/`, using +[`systemd.packages`](options.html#opt-systemd.packages) will make you able to start the service via `systemctl --user start`, but it won\'t start automatically on login. However, You can imperatively -enable it by adding the package\'s attribute to [ -`systemd.packages`](#opt-environment.systemPackages) and then do this -(e.g): +enable it by adding the package\'s attribute to +[`systemd.packages`](options.html#opt-systemd.packages) +and then do this (e.g): ```ShellSession $ mkdir -p ~/.config/systemd/user/default.target.wants diff --git a/nixos/doc/manual/from_md/administration/service-mgmt.chapter.xml b/nixos/doc/manual/from_md/administration/service-mgmt.chapter.xml index 0e1fceb50d07b..68dc45f3f88a3 100644 --- a/nixos/doc/manual/from_md/administration/service-mgmt.chapter.xml +++ b/nixos/doc/manual/from_md/administration/service-mgmt.chapter.xml @@ -25,7 +25,7 @@ explains NixOS specific things worth knowing. </para> <para> - Without any arguments, <literal>systmctl</literal> the status of + Without any arguments, <literal>systemctl</literal> the status of active units: </para> <programlisting> @@ -109,12 +109,13 @@ systemd.packages = [ pkgs.packagekit ]; <emphasis>User</emphasis> systemd services on the other hand, should be treated differently. Given a package that has a systemd unit file at <literal>#pkg-out#/lib/systemd/user/</literal>, using - <xref linkend="opt-systemd.packages" /> will make you able to - start the service via <literal>systemctl --user start</literal>, - but it won't start automatically on login. However, You can - imperatively enable it by adding the package's attribute to - <link linkend="opt-environment.systemPackages"> - <literal>systemd.packages</literal></link> and then do this (e.g): + <link xlink:href="options.html#opt-systemd.packages"><literal>systemd.packages</literal></link> + will make you able to start the service via + <literal>systemctl --user start</literal>, but it won't start + automatically on login. However, You can imperatively enable it by + adding the package's attribute to + <link xlink:href="options.html#opt-systemd.packages"><literal>systemd.packages</literal></link> + and then do this (e.g): </para> <programlisting> $ mkdir -p ~/.config/systemd/user/default.target.wants |