2 .\" Title: systemd.mount
3 .\" Author: Lennart Poettering <lennart@poettering.net>
4 .\" Generator: DocBook XSL Stylesheets v1.76.1 <http://docbook.sf.net/>
6 .\" Manual: systemd.mount
10 .TH "SYSTEMD\&.MOUNT" "5" "02/15/2012" "systemd" "systemd.mount"
11 .\" -----------------------------------------------------------------
12 .\" * Define some portability stuff
13 .\" -----------------------------------------------------------------
14 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
15 .\" http://bugs.debian.org/507673
16 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
17 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
20 .\" -----------------------------------------------------------------
21 .\" * set default formatting
22 .\" -----------------------------------------------------------------
23 .\" disable hyphenation
25 .\" disable justification (adjust text to left margin only)
27 .\" -----------------------------------------------------------------
28 .\" * MAIN CONTENT STARTS HERE *
29 .\" -----------------------------------------------------------------
31 systemd.mount \- systemd mount configuration files
37 A unit configuration file whose name ends in
39 encodes information about a file system mount point controlled and supervised by systemd\&.
41 This man page lists the configuration options specific to this unit type\&. See
43 for the common options of all unit configuration files\&. The common configuration items are configured in the generic [Unit] and [Install] sections\&. The mount specific configuration options are configured in the [Mount] section\&.
45 Additional options are listed in
46 \fBsystemd.exec\fR(5), which define the execution environment the
48 binary is executed in\&.
50 Mount units must be named after the mount point directories they control\&. Example: the mount point
52 must be configured in a unit file
53 home\-lennart\&.mount\&. For details about the escaping logic used to convert a file system path to a unit name see
54 \fBsystemd.unit\fR(5)\&.
56 Optionally, a mount unit may be accompanied by an automount unit, to allow on\-demand or parallelized mounting\&. See
57 \fBsystemd.automount\fR(5)\&.
59 If an mount point is beneath another mount point in the file system hierarchy, a dependency between both units is created automatically\&.
61 Mount points created at runtime independent on unit files or
63 will be monitored by systemd and appear like any other mount unit in systemd\&.
66 Mount units may either be configured via unit files, or via
74 a few special mount options are understood by systemd which influence how dependencies are created for mount points from
79 (which is the default), or if
80 \fBx\-systemd\&.mount\fR
81 is specified as mount option, then systemd will create a dependency of type
86 remote\-fs\&.target, depending whether the file system is local or remote\&. If
87 \fBx\-systemd\&.automount\fR
88 is set, an automount unit will be created for the file system\&. See
89 \fBsystemd.automount\fR(5)
91 \fBx\-systemd\-device\-timeout=\fR
92 is specified it may be used to configure how long systemd should wait for a device to show up before giving up on an entry from
93 /etc/fstab\&. Specify a time in seconds or explicitly specifiy a unit as
99 If a mount point is configured in both
101 and a unit file, the configuration in the latter takes precedence\&.
104 Mount files must include a [Mount] section, which carries information about the file system mount points it supervises\&. A number of options that may be used in this section are shared with other unit types\&. These options are documented in
105 \fBsystemd.exec\fR(5)\&. The options specific to the [Mount] section of mount units are the following:
109 Takes an absolute path of a device node, file or other resource to mount\&. See
111 for details\&. If this refers to a device node, a dependency on the respective device unit is automatically created\&. (See
112 \fBsystemd.device\fR(5)
113 for more information\&.) This option is mandatory\&.
118 Takes an absolute path of a directory of the mount point\&. If the mount point is not existing at time of mounting, it is created\&. This string must be reflected in the unit file name\&. (See above\&.) This option is mandatory\&.
123 Takes a string for the filesystem type\&. See
125 for details\&. This setting is optional\&.
130 Mount options to use when mounting\&. This takes a comma separated list of options\&. This setting is optional\&.
135 Directories of mount points (and any parent directories) are automatically created if needed\&. This option specifies the file system access mode used when creating these directories\&. Takes an access mode in octal notation\&. Defaults to 0755\&.
140 Configures the time to wait for the mount command to finish\&. If a command does not exit within the configured time the mount will be considered failed and be shut down again\&. All commands still running will be terminated forcibly via SIGTERM, and after another delay of this time with SIGKILL\&. (See
142 below\&.) Takes a unit\-less value in seconds, or a time span value such as "5min 20s"\&. Pass 0 to disable the timeout logic\&. Defaults to 90s\&.
147 Specifies how processes of this mount shall be killed\&. One of
148 \fBcontrol\-group\fR,
152 This option is mostly equivalent to the
154 option of service files\&. See
155 \fBsystemd.service\fR(5)
161 Specifies which signal to use when killing a process of this mount\&. Defaults to SIGTERM\&.
166 Specifies whether to send SIGKILL to remaining processes after a timeout, if the normal shutdown procedure left processes of the mount around\&. Takes a boolean value\&. Defaults to "yes"\&.
173 \fBsystemd.unit\fR(5),
174 \fBsystemd.exec\fR(5),
175 \fBsystemd.device\fR(5),
179 \fBLennart Poettering\fR <\&lennart@poettering\&.net\&>