···

       
22
       
22
       
 
       
# systemctl kexec

     

       
23
       
23
       
 
       
```

     

       
24
       
24
       
 
       


     

       
25
       
25
       
-
       
The machine can be suspended to RAM (if supported) using `systemctl

     

       
26
       
26
       
-
       
  suspend`, and suspended to disk using `systemctl

     

       
27
       
27
       
-
       
  hibernate`.

     

       
25
       
25
       
+
       
The machine can be suspended to RAM (if supported) using `systemctl suspend`,

     

       
26
       
26
       
+
       
and suspended to disk using `systemctl hibernate`.

     

       
28
       
27
       
 
       


     

       
29
       
28
       
 
       
These commands can be run by any user who is logged in locally, i.e. on

     

       
30
       
29
       
 
       
a virtual console or in X11; otherwise, the user is asked for

     

···

       
20
       
20
       
 
       
](#sect-nixos-systemd-nixos) explains NixOS specific things worth

     

       
21
       
21
       
 
       
knowing.

     

       
22
       
22
       
 
       


     

       
23
       
23
       
-
       
Without any arguments, `systmctl` the status of active units:

     

       
23
       
23
       
+
       
Without any arguments, `systemctl` the status of active units:

     

       
24
       
24
       
 
       


     

       
25
       
25
       
 
       
```ShellSession

     

       
26
       
26
       
 
       
$ systemctl

     
···

       
96
       
96
       
 
       


     

       
97
       
97
       
 
       
*User* systemd services on the other hand, should be treated

     

       
98
       
98
       
 
       
differently. Given a package that has a systemd unit file at

     

       
99
       
99
       
-
       
`#pkg-out#/lib/systemd/user/`, using [](#opt-systemd.packages) will

     

       
99
       
99
       
+
       
`#pkg-out#/lib/systemd/user/`, using

     

       
100
       
100
       
+
       
[`systemd.packages`](options.html#opt-systemd.packages) will

     

       
100
       
101
       
 
       
make you able to start the service via `systemctl --user start`, but it

     

       
101
       
102
       
 
       
won\'t start automatically on login. However, You can imperatively

     

       
102
       
102
       
-
       
enable it by adding the package\'s attribute to [

     

       
103
       
103
       
-
       
`systemd.packages`](#opt-environment.systemPackages) and then do this

     

       
104
       
104
       
-
       
(e.g):

     

       
103
       
103
       
+
       
enable it by adding the package\'s attribute to

     

       
104
       
104
       
+
       
[`systemd.packages`](options.html#opt-systemd.packages)

     

       
105
       
105
       
+
       
and then do this (e.g):

     

       
105
       
106
       
 
       


     

       
106
       
107
       
 
       
```ShellSession

     

       
107
       
108
       
 
       
$ mkdir -p ~/.config/systemd/user/default.target.wants

     

···

       
25
       
25
       
 
       
      explains NixOS specific things worth knowing.

     

       
26
       
26
       
 
       
    </para>

     

       
27
       
27
       
 
       
    <para>

     

       
28
       
28
       
-
       
      Without any arguments, <literal>systmctl</literal> the status of

     

       
28
       
28
       
+
       
      Without any arguments, <literal>systemctl</literal> the status of

     

       
29
       
29
       
 
       
      active units:

     

       
30
       
30
       
 
       
    </para>

     

       
31
       
31
       
 
       
    <programlisting>

     
···

       
109
       
109
       
 
       
      <emphasis>User</emphasis> systemd services on the other hand,

     

       
110
       
110
       
 
       
      should be treated differently. Given a package that has a systemd

     

       
111
       
111
       
 
       
      unit file at <literal>#pkg-out#/lib/systemd/user/</literal>, using

     

       
112
       
112
       
-
       
      <xref linkend="opt-systemd.packages" /> will make you able to

     

       
113
       
113
       
-
       
      start the service via <literal>systemctl --user start</literal>,

     

       
114
       
114
       
-
       
      but it won't start automatically on login. However, You can

     

       
115
       
115
       
-
       
      imperatively enable it by adding the package's attribute to

     

       
116
       
116
       
-
       
      <link linkend="opt-environment.systemPackages">

     

       
117
       
117
       
-
       
      <literal>systemd.packages</literal></link> and then do this (e.g):

     

       
112
       
112
       
+
       
      <link xlink:href="options.html#opt-systemd.packages"><literal>systemd.packages</literal></link>

     

       
113
       
113
       
+
       
      will make you able to start the service via

     

       
114
       
114
       
+
       
      <literal>systemctl --user start</literal>, but it won't start

     

       
115
       
115
       
+
       
      automatically on login. However, You can imperatively enable it by

     

       
116
       
116
       
+
       
      adding the package's attribute to

     

       
117
       
117
       
+
       
      <link xlink:href="options.html#opt-systemd.packages"><literal>systemd.packages</literal></link>

     

       
118
       
118
       
+
       
      and then do this (e.g):

     

       
118
       
119
       
 
       
    </para>

     

       
119
       
120
       
 
       
    <programlisting>

     

       
120
       
121
       
 
       
$ mkdir -p ~/.config/systemd/user/default.target.wants