summaryrefslogtreecommitdiffstats
path: root/man/systemd.mount.xml (follow)
Commit message (Collapse)AuthorAgeFilesLines
* man: do not say "additional symlinks" for mount/automount aliasesZbigniew Jędrzejewski-Szmek2022-05-261-6/+7
| | | | | "additional" implies that the unit itself is a symlink, which it is not. Also "link to the mount unit", not "link to the mount".
* man: tweak description of auto/noautoZbigniew Jędrzejewski-Szmek2022-03-041-5/+7
| | | | | | | | | | | I think the current behaviour is stupid: 'x-systemd.automount,noauto' should mean that we create the units, but don't add .mount or .automount to any targets. Instead, we completely ignore 'noauto'. But let's at least describe the implementation. Text suggested by dpartrid in the bug. Fixes #21040.
* man: mention pages with more settings at end of each option listZbigniew Jędrzejewski-Szmek2021-09-271-7/+7
| | | | | | | | | | | For some unit types we have hundreds of options, and the reader may easily miss that more options are described in other pages. We already mentioned this in the introduction and then at the top of the option list, but it can't hurt to repeat the information. Also, add an (almost empty) Options section for the unit types which don't have any custom options. It is nicer to have the same page structure in all cases, so people can jump between pages for different types more easily.
* license: LGPL-2.1+ -> LGPL-2.1-or-laterYu Watanabe2020-11-091-1/+1
|
* man: use trailing slash on directories in more placesZbigniew Jędrzejewski-Szmek2020-10-051-4/+4
|
* Merge pull request #16143 from fbuihuu/fstab-generator-fixZbigniew Jędrzejewski-Szmek2020-07-071-2/+10
|\ | | | | fstab-generator: make sure explicit deps configured via mount options apply to .mount, not .automount unit
| * fstab-generator: extra dependencies specified in fstab should be applied to ↵Franck Bui2020-07-011-2/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | the mount unit If an entry in fstab uses "x-systemd.automount" option and also asks for additionnal dependencies via x-systemd.requires or such, then the dependencies were applied to the automount unit. But this unlikely to do the right thing and is inconsistent with what's done for network mounts. Indeed when an fstab entries has "_netdev,x-systemd.automount" options, the dependencies against the network requested by "_netdev" are (correctly) applied to the mount unit only and the automount unit remains ordered against local-fs.target. The same logic should be followed when extra deps are specified via the mount options as automount units should always be ordered against local-fs.target. Note: in general explicit deps specified via mount options should be used with care and should be used to specify dependencies on other mount units only as it can easily create ordering cycles otherwise like it's been seen in https://github.com/systemd/systemd-stable/issues/69. Mount units (as well as automount ones) are ordered before local-fs.target by default which is a low-level target that most other units depend on.
* | tree-wide: drop quotes from around [section]Zbigniew Jędrzejewski-Szmek2020-07-061-3/+3
|/ | | | | | | For users, the square brackets already serve as markup and clearly delineate the section name from surrounding text. Putting additional markup around that only adds clutter. Also, we were very inconsistent in using the quotes. Let's just drop them altogether.
* Merge pull request #15661 from hundeboll/mount-read-write-onlyZbigniew Jędrzejewski-Szmek2020-05-201-0/+24
|\ | | | | Mount read write only
| * man: document x-systemd.rw-only fstab optionMartin Hundebøll2020-05-201-0/+11
| |
| * man: document ReadWriteOnly property for mount unitsMartin Hundebøll2020-05-201-0/+13
| |
* | man: put all pages which mention a specifier in the indexZbigniew Jędrzejewski-Szmek2020-05-071-4/+4
|/ | | | | | I wasn't 100% convinced that this is the right thing to do, hence the separate commit. But e.g. for paths we index all mentions, so I think it's reasonable to do the same here.
* Implemented x-systemd.{required,wanted}-by= optionsAntonio Russo2020-01-211-0/+15
| | | | | | | | | | | | Teaches systemd-fstab-generator these two unit options, creating appropriate dependencies on the generated .mount units. When used, they override any other automatically generated dependencies, such as local-fs.target, and are NOT suppressed by noauto. The new options are ignored for /, in the same way that noauto is ignored. Fixes: #14380 Signed-off-by: Antonio Russo <antonio.e.russo@gmail.com>
* Documentation update for x-systemd.{before,after}Antonio Russo2020-01-211-3/+3
| | | | | | A minor clarification in the manual page is made. Signed-off-by: Antonio Russo <antonio.e.russo@gmail.com>
* man: we support bind mounting regular files tooLennart Poettering2020-01-131-6/+4
| | | | | Let's be precise here: we accept non-directories here too, even though we create things as directories if we find the Where= not to exist.
* man: document that we mkdir() on What= in .mount units tooLennart Poettering2020-01-131-6/+10
| | | | | | As suggested here: https://lists.freedesktop.org/archives/systemd-devel/2020-January/043914.html
* man: change noindex="true" to index="false"Zbigniew Jędrzejewski-Szmek2019-11-211-1/+1
| | | | We nowadays prefer positive options over negative.
* man: Add missing <literal> tags in various man pagesPhilip Withnall2019-06-121-3/+3
| | | | | | | A minor formatting improvement brought to you by the wonders of `git grep`. Signed-off-by: Philip Withnall <withnall@endlessm.com>
* man: add missing =Zbigniew Jędrzejewski-Szmek2019-05-171-1/+1
| | | | Fixes #12598.
* codespell: fix spelling errorsBen Boeckel2019-04-291-1/+1
|
* man: add references from the .mount and .service man pages to ↵Lennart Poettering2019-04-081-1/+7
| | | | | | systemd-{mount,run} pages Fixes: #12235
* man: use same header for all filesZbigniew Jędrzejewski-Szmek2019-03-141-1/+1
| | | | | | | The "include" files had type "book" for some raeason. I don't think this is meaningful. Let's just use the same everywhere. $ perl -i -0pe 's^..DOCTYPE (book|refentry) PUBLIC "-//OASIS//DTD DocBook XML V4.[25]//EN"\s+"http^<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"\n "http^gms' man/*.xml
* man: standarize on one-line license headerZbigniew Jędrzejewski-Szmek2019-03-141-4/+1
| | | | | | No need to waste space, and uniformity is good. $ perl -i -0pe 's|\n+<!--\s*SPDX-License-Identifier: LGPL-2.1..\s*-->|\n<!-- SPDX-License-Identifier: LGPL-2.1+ -->|gms' man/*.xml
* man: clarify the source of DefaultTimeoutStartSec=Yu Watanabe2019-02-011-3/+4
|
* man: update DefaultDependency= in systemd.mount(5)Yu Watanabe2019-01-261-2/+6
| | | | | Follow-up for d54bab90e64f70c1ecf9b0683a98adb8485ed09e and the previous commit.
* man: Use the proper option name in documentationMichael Scherer2018-12-131-1/+1
|
* man: add missing descriptions of fstab options to systemd.swap(5)Zbigniew Jędrzejewski-Szmek2018-12-031-2/+2
|
* man: document that 'nofail' also has an effect on orderingLennart Poettering2018-08-021-6/+4
| | | | Prompted by #9765
* man: drop unused <authorgroup> tags from man sourcesZbigniew Jędrzejewski-Szmek2018-06-141-9/+0
| | | | | | | | | | | | Docbook styles required those to be present, even though the templates that we use did not show those names anywhere. But something changed semi-recently (I would suspect docbook templates, but there was only a minor version bump in recent years, and the changelog does not suggest anything related), and builds now work without those entries. Let's drop this dead weight. Tested with F26-F29, debian unstable. $ perl -i -0pe 's/\s*<authorgroup>.*<.authorgroup>//gms' man/*xml
* tree-wide: remove Lennart's copyright linesLennart Poettering2018-06-141-2/+0
| | | | | | | | | | | These lines are generally out-of-date, incomplete and unnecessary. With SPDX and git repository much more accurate and fine grained information about licensing and authorship is available, hence let's drop the per-file copyright notice. Of course, removing copyright lines of others is problematic, hence this commit only removes my own lines and leaves all others untouched. It might be nicer if sooner or later those could go away too, making git the only and accurate source of authorship information.
* tree-wide: drop 'This file is part of systemd' blurbLennart Poettering2018-06-141-2/+0
| | | | | | | | | | | | | | | | This part of the copyright blurb stems from the GPL use recommendations: https://www.gnu.org/licenses/gpl-howto.en.html The concept appears to originate in times where version control was per file, instead of per tree, and was a way to glue the files together. Ultimately, we nowadays don't live in that world anymore, and this information is entirely useless anyway, as people are very welcome to copy these files into any projects they like, and they shouldn't have to change bits that are part of our copyright header for that. hence, let's just get rid of this old cruft, and shorten our codebase a bit.
* doc: more spelling fixesMichael Biebl2018-06-121-1/+1
|
* man: merge two sections into two subsections of one sectionZbigniew Jędrzejewski-Szmek2018-04-181-45/+49
| | | | Those are very close subjects that are a good fit for one section.
* tree-wide: drop license boilerplateZbigniew Jędrzejewski-Szmek2018-04-061-13/+0
| | | | | | | | | | Files which are installed as-is (any .service and other unit files, .conf files, .policy files, etc), are left as is. My assumption is that SPDX identifiers are not yet that well known, so it's better to retain the extended header to avoid any doubt. I also kept any copyright lines. We can probably remove them, but it'd nice to obtain explicit acks from all involved authors before doing that.
* man: User=, Group= *never* work for mount units (#7602)Alan Jenkins2017-12-191-6/+10
| | | | | | | | | | | | | | | | | | | | | | | | Old text: > Note that the User= and > Group= options are not particularly useful for mount units specifying a > "Type=" option or using configuration not specified in /etc/fstab; > mount(8) will refuse options that are not listed in /etc/fstab if it is > not run as UID 0. However I recently learnt the following: > The mount program does not read the /etc/fstab file if both device > and dir are specified. Therefore, if both device and dir are specified, the `user` or `users` options in `fstab` will not have any effect. Run as a normal user, you will always see mount: only root can do that Fix the explanation in the man page. Also make sure to markup User= and Group= with <varname>.
* man: generalize "binary" to "program" (#7668)Alan Jenkins2017-12-161-1/+1
| | | | | | | | | | | Systemd services are permitted to be scripts, as well as binary executables. The same also applies to the underlying /sbin/mount and /sbin/swapon. It is not necessary for the user to consider what type of program file these are. Nor is it necessary with systemd-nspawn, to distinguish between init as a "binary" v.s. a user-specified "program". Also fix a couple of grammar nits in the modified sentences.
* man: add docs for systemd-growfs and systemd-makefsZbigniew Jędrzejewski-Szmek2017-11-301-0/+38
|
* Add SPDX license identifiers to man pagesZbigniew Jędrzejewski-Szmek2017-11-191-0/+2
|
* man: document that noauto doesn't affect automount units configured through ↵Lennart Poettering2017-11-161-7/+6
| | | | | /etc/fstab (#7350) Fixes: #6937
* man: explicitly distinguish "implicit dependencies" and "default dependencies"John Lin2017-09-131-32/+49
| | | | Fixes: #6793
* man: add an explicit description of _netdev to systemd.mount(5)Zbigniew Jędrzejewski-Szmek2017-09-051-0/+17
| | | | | It was mentioned in passing, but having it in the list of options is also nice.
* fstab-generator: Chase symlinks where possible (#6293)Colin Walters2017-07-111-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | This has a long history; see see 5261ba901845c084de5a8fd06500ed09bfb0bd80 which originally introduced the behavior. Unfortunately that commit doesn't include any rationale, but IIRC the basic issue is that systemd wants to model the real mount state as units, and symlinks make canonicalization much more difficult. At the same time, on a RHEL6 system (upstart), one can make e.g. `/home` a symlink, and things work as well as they always did; but one doesn't have access to the sophistication of mount units (dependencies, introspection, etc.) Supporting symlinks here will hence make it easier for people to do upgrades to RHEL7 and beyond. The `/home` as symlink case also appears prominently for OSTree; see https://ostree.readthedocs.io/en/latest/manual/adapting-existing/ Further work has landed in the nspawn case for this; see e.g. d944dc9553009822deaddec76814f5642a6a8176 A basic limitation with doing this in the fstab generator (and that I hit while doing some testing) is that we obviously can't chase symlinks into mounts, since the generator runs early before mounts. Or at least - doing so would require multiple passes over the fstab data (as well as looking at existing mount units), and potentially doing multi-phase generation. I'm not sure it's worth doing that without a real world use case. For now, this will fix at least the OSTree + `/home` <https://bugzilla.redhat.com/show_bug.cgi?id=1382873> case mentioned above, and in general anyone who for whatever reason has symlinks in their `/etc/fstab`.
* fstab-generator: handle NFS "bg" mounts correctly. (#6103)NeilBrown2017-07-041-2/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When "bg" is specified for NFS mounts, and if the server is not accessible, two behaviors are possible depending on networking details. If a definitive error is received, such a EHOSTUNREACH or ECONNREFUSED, mount.nfs will fork and continue in the background, while /bin/mount will report success. If no definitive error is reported but the connection times out instead, then the mount.nfs timeout will normally be longer than the systemd.mount timeout, so mount.nfs will be killed by systemd. In the first case the mount has appeared to succeed even though it hasn't. This can be confusing. Also the background mount.nfs will never get cleaned up, even if the mount unit is stopped. In the second case, mount.nfs is killed early and so the mount will not complete when the server comes back. Neither of these are ideal. This patch modifies the options when an NFS bg mount is detected to force an "fg" mount, but retain the default "retry" time of 10000 minutes that applies to "bg" mounts. It also imposes "nofail" behaviour and sets the TimeoutSec for the mount to "infinity" so the retry= time is allowed to complete. This provides near-identical behaviour to an NFS bg mount started directly by "mount -a". The only difference is that systemd will not wait for the first mount attempt, while "mount -a" will. Fixes #6046
* man: fix links to external man pagesZbigniew Jędrzejewski-Szmek2017-05-071-1/+1
| | | | linkchecker ftw!
* man: use https:// in URLsAsciiWolf2017-02-211-1/+1
|
* fstab-generator: add x-systemd.before and x-systemd.after fstab options (#5330)Ruslan Bilovol2017-02-131-0/+19
| | | | | | | | | | | | | | | | | | | | | | Currently fstab entries with 'nofail' option are mounted asynchronously and there is no way how to specify dependencies between such fstab entry and another units. It means that users are forced to write additional dependency units manually. The patch introduces new systemd fstab options: x-systemd.before=<PATH> x-systemd.after=<PATH> - to specify another mount dependency (PATH is translated to unit name) x-systemd.before=<UNIT> x-systemd.after=<UNIT> - to specify arbitrary UNIT dependency For example mount where A should be mounted before local-fs.target unit: /dev/sdb1 /mnt/test/A none nofail,x-systemd.before=local-fs.target
* fstab-generator: also convert % → %% for What=Lennart Poettering2017-02-081-8/+6
| | | | Same reasons as the previous patch.
* fstab-generator: Options= applies specifier expansionLennart Poettering2017-02-081-3/+3
| | | | | | | Let's document that this is the case, and properly escape % when we generate Options= in the generator. Fixes: #5086
* core: make mount units from /proc/self/mountinfo possibly bind to a device ↵Franck Bui2016-12-161-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | (#4515) Since commit 9d06297, mount units from mountinfo are not bound to their devices anymore (they use the "Requires" dependency instead). This has the following drawback: if a media is mounted and the eject button is pressed then the media is unconditionally ejected leaving some inconsistent states. Since udev is the component that is reacting (no matter if the device is used or not) to the eject button, users expect that udev at least try to unmount the media properly. This patch introduces a new property "SYSTEMD_MOUNT_DEVICE_BOUND". When set on a block device, all units that requires this device will see their "Requires" dependency upgraded to a "BindTo" one. This is currently only used by cdrom devices. This patch also gives the possibility to the user to restore the previous behavior that is bind a mount unit to a device. This is achieved by passing the "x-systemd.device-bound" option to mount(8). Please note that currently this is not working because libmount treats the x-* options has comments therefore they're not available in utab for later application retrievals.
* fstab-generator: add x-systemd.mount-timeout (#4603)Christian Hesse2016-11-111-0/+19
| | | | | | | | | | This adds a new systemd fstab option x-systemd.mount-timeout. The option adds a timeout value that specifies how long systemd waits for the mount command to finish. It allows to mount huge btrfs volumes without issues. This is equivalent to adding option TimeoutSec= to [Mount] section in a mount unit file. fixes #4055
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-03 11:49:05 +0100