X-Git-Url: http://git.ipfire.org/?a=blobdiff_plain;f=man%2Fsystemd-mount.xml;h=4a7c33f5584244261e9de09cc7f9fe25ab09849e;hb=5057d73ba1bb016c9325d0a7fdb84519d3443622;hp=76ea0550d79d72f413959ad4ef78905b45dbfa8d;hpb=4579e8ef313efe56f99a4bdd43439c508a6d49ce;p=thirdparty%2Fsystemd.git diff --git a/man/systemd-mount.xml b/man/systemd-mount.xml index 76ea0550d79..4a7c33f5584 100644 --- a/man/systemd-mount.xml +++ b/man/systemd-mount.xml @@ -1,27 +1,7 @@ - - - - + + + @@ -29,15 +9,6 @@ systemd-mount systemd - - - - Developer - Lennart - Poettering - lennart@poettering.net - - @@ -84,13 +55,14 @@ the service manager job queue, so that it may pull in further dependencies (such as parent mounts, or a file system checker to execute a priori), and may make use of the auto-mounting logic. - The command takes either one or two arguments. If only one argument is specified it should refer to a block - device or regular file containing a file system (e.g. /dev/sdb1 or - /path/to/disk.img). If it is a block device, which is then probed for a label and other - metadata, and is mounted to a directory whose name is generated from the label. In this mode the block device must - exist at the time of invocation of the command, so that it may be probed. If the device is found to be a removable - block device (e.g. a USB stick) an automount point instead of a regular mount point is created (i.e. the - option is implied, see below). + The command takes either one or two arguments. If only one argument is specified it should refer to + a block device or regular file containing a file system (e.g. /dev/sdb1 or + /path/to/disk.img). The block device or image file is then probed for a file system + label and other metadata, and is mounted to a directory below /run/media/system/ + whose name is generated from the file system label. In this mode the block device or image file must + exist at the time of invocation of the command, so that it may be probed. If the device is found to be a + removable block device (e.g. a USB stick) an automount point instead of a regular mount point is created + (i.e. the option is implied, see below). If two arguments are specified the first indicates the mount source (the WHAT) and the second indicates the path to mount it on (the WHERE). In this mode no probing of the @@ -140,7 +112,7 @@ the command line. If passed, additional metadata is read from the device to enhance the unit to create. For example, a descriptive string for the transient units is generated from the file system label and device model. Moreover if a removable block device (e.g. USB stick) is detected an automount unit instead of a regular - mount unit is created, with a short idle time-out, in order to ensure the file-system is placed in a clean + mount unit is created, with a short idle timeout, in order to ensure the file-system is placed in a clean state quickly after each access. @@ -239,11 +211,11 @@ - + - Takes a boolean argument, defaults to off. This option only has an effect in automount mode, - and controls whether the automount unit shall be bound to the backing device's lifetime. If enabled, the - automount point will be removed automatically when the backing device vanishes. If disabled the automount point + This option only has an effect in automount mode, + and controls whether the automount unit shall be bound to the backing device's lifetime. If set, the + automount point will be removed automatically when the backing device vanishes. By default the automount point stays around, and subsequent accesses will block until backing device is replugged. This option has no effect in case of non-device mounts, such as network or virtual file system mounts. @@ -282,7 +254,7 @@ all mount units that mount and failed are kept in memory until the user explicitly resets their failure state with systemctl reset-failed or an equivalent command. On the other hand, units that stopped successfully are unloaded immediately. If this option is turned on the "garbage collection" of units is more - agressive, and unloads units regardless if they exited successfully or failed. This option is a shortcut for + aggressive, and unloads units regardless if they exited successfully or failed. This option is a shortcut for --property=CollectMode=inactive-or-failed, see the explanation for CollectMode= in systemd.unit5 for further @@ -329,6 +301,15 @@ + + Example + + Use a udev rule like the following to automatically mount all USB storage plugged in: + + ACTION=="add", SUBSYSTEMS=="usb", SUBSYSTEM=="block", ENV{ID_FS_USAGE}=="filesystem", \ + RUN{program}+="/usr/bin/systemd-mount --no-block --automount=yes --collect $devnode" + + See Also