summaryrefslogtreecommitdiff
path: root/man/tmpfiles.d.xml
Commit message (Collapse)AuthorAgeFilesLines
* man: document new specifiersLennart Poettering2020-04-281-1/+7
|
* Typo fixbemarek2020-03-091-1/+1
|
* man: tmpfiles.d: z/Z ignore the argumentTopi Miettinen2020-02-181-2/+2
| | | | | The argument is not used for any MAC context by z and Z, so drop the confusing text from the table.
* man: tmpfiles.d: list missing qFlorian Klink2020-01-261-1/+2
| | | | | Also, Q creates directories (same as v), so update the example accordingly.
* man: tmpfiles.d: only list "v" onceAnsgar Burchardt2020-01-031-1/+0
|
* man: tmpfiles.d: "b", "c" options require major and minor numbersAnsgar Burchardt2020-01-031-4/+4
|
* [man] fix URLAnita Zhang2019-12-181-1/+1
|
* man: fix a few bogus entries in directives indexZbigniew Jędrzejewski-Szmek2019-11-211-1/+1
| | | | | | When wrong element types are used, directives are sometimes placed in the wrong section. Also, strip part of text starting with "'", which is used in a few places and which is displayed improperly in the index.
* man: change noindex="true" to index="false"Zbigniew Jędrzejewski-Szmek2019-11-211-1/+1
| | | | We nowadays prefer positive options over negative.
* systemd-tmpfiles: cleanup man page program listingZach Smith2019-11-081-2/+8
|
* systemd-tmpfiles: deprecate F for f+Zach Smith2019-10-311-11/+8
|
* systemd-tmpfiles: allow appending content to fileZach Smith2019-10-031-8/+8
| | | | | | | Adds support to append to files with w+ type. w /tmp/13291.out - - - - first line\n w+ /tmp/13291.out - - - - second line\n
* man: highlight the different concepts behind h/H and t/TLennart Poettering2019-07-241-33/+34
| | | | Fixes: #13151
* Merge pull request #12750 from keszybz/tmpfiles-c-copyLennart Poettering2019-07-111-0/+31
|\ | | | | Make tmpfiles C use --root
| * man: add "quick reference" to tmpfiles.d(5)Zbigniew Jędrzejewski-Szmek2019-06-051-0/+31
| | | | | | | | | | | | The synopsis section would describe config file paths, but not their syntax. Let's add a short table that so that it's possible to quickly remind oneself what the different letter mean.
* | man: document tmpfiles.d/ user/group resolvability needsLennart Poettering2019-07-031-0/+8
|/
* tmpfiles: support the FS_PROJINHERIT_FL chattr flagLennart Poettering2019-03-281-9/+5
|
* man: use same header for all filesZbigniew Jędrzejewski-Szmek2019-03-141-1/+2
| | | | | | | 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: document the new BSD file lock logic in tmpfilesLennart Poettering2019-02-151-0/+8
|
* Fixed minor typo in man/tmpfiles.d.xmlRonnie P. Thomas2019-01-301-1/+1
|
* tmpfiles: Make C still copy if the destination directory is emptyRyan Gonzalez2019-01-081-5/+5
| | | | Fixes #11287.
* man: add a note that /var/run should not be used in tmpfilesZbigniew Jędrzejewski-Szmek2018-12-111-0/+7
|
* man: rewrite the general description of tmpfilesZbigniew Jędrzejewski-Szmek2018-12-111-16/+27
| | | | | | | | | We would describe tmpfiles.d through what systemd-tmpfiles does with them, but I think it's better to start with a geneneral statement what they are. Also, let's make the description of volatile file systems less prominent. Also, strenghten the advice to use RuntimeDirectory and mention {Cache,Logs,Configuration,State}Directory=.
* man: reword tmpfiles.d descriptions to refer less to previous descriptionsZbigniew Jędrzejewski-Szmek2018-12-111-56/+56
| | | | | | | | | | | | | | | | | I think it is OK if some option is described as "similar to ..., but in addition ...", as long as the "in addition" part is strictly additive this is unambiguous. Otherwise, we'd have to repeat a lot of text, and then we'd probably forget to adjust some of the descriptions when doing changes. But when the "in addition" part is about replacing or removing parts of functionality, it is better to avoid this pattern and describe the later option from scratch. Some paragraph breaks are added and minor changes made. UID/GID is changed to user/group, since we generally expect user/group names to be used, not numeric ids. Fixes #11115.
* man: minor fixesLennart Poettering2018-11-201-3/+3
| | | | | | As suggested here: https://github.com/systemd/systemd/pull/10538#pullrequestreview-176710207
* man: document that for removal tmpfiles.d prefix is run after suffixLennart Poettering2018-11-081-22/+14
|
* man: stop mentioning /var/run in tmpfiles.d(5)Lennart Poettering2018-11-081-6/+3
| | | | | | It's obsolete, stop mentioning it. Let's not confuse people suggests it would be OK to use that, because it really isn't anymore, and it gives us trouble with merging idenctical lines.
* shared: add %g, %G specifiers for group / gid (#10368)Davide Cavalca2018-10-131-0/+10
|
* man: fix explanation about UID/GID field in tmpfiles.d(5)Yu Watanabe2018-10-051-10/+5
| | | | Fixes #9495.
* RFC tmpfiles: Allow configuration to ignore execution errorsWilliam Douglas2018-09-251-1/+10
| | | | | | | | This is an implementation that covers making errors encountered when writing file content optionally fatal. If this is something that folks would want I'll add handling of this for all the other directives. I'd appreciate suggestions on how this might better be structured as well (use of a goto fail or such) as I'm not super happy with the approach.
* tmpfiles: don't adjust qgroups on existing subvolumesFranck Bui2018-08-081-58/+37
| | | | | | | | | | The qgroup logic (types 'q' and 'Q') only has an effect if there's no previous setup at all, and any explicitly configured subvolumes with their qgroups are left entirely unmodified. The idea is that if users want a different logic than the one we set up by default, then by all means they should do that before hand, and tmpfiles won't override their logic.
* Merge pull request #9489 from keszybz/copyright-removal-3Lennart Poettering2018-07-031-1/+1
|\ | | | | Copyright header removal, part 3 (or 4?)
| * man: drop mode line in file headersZbigniew Jędrzejewski-Szmek2018-07-031-1/+1
| | | | | | | | | | This is already included in .dir-locals, so we don't need it in the files themselves.
* | man: add missing <option> tagLucas Werkmeister2018-07-031-1/+1
|/ | | | | | | One mention of --user was missing the surrounding <option> tag, making the table look inconsistent (though the inconsistency is less obvious after the reordering in 709f4c472c, since the four specifiers mentioning the --user option are no longer immediately adjacent).
* 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: beautify remaining copyright statementsLennart Poettering2018-06-141-1/+1
| | | | | | Let's unify an beautify our remaining copyright statements, with a unicode ©. This means our copyright statements are now always formatted the same way. Yay.
* 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.
* man: don't refer to "service manager" in tmpfiles.d(5)Lennart Poettering2018-05-291-3/+3
| | | | system-tmpfiles is not a "service manager" hence say "command" instead.
* core: introduce specifiers for /tmp and /var/tmpLennart Poettering2018-05-291-0/+10
| | | | | | | | | | | This corresponds nicely with the specifiers we already pass for /var/lib, /var/cache, /run and so on. This is particular useful to update the test-path service files to operate without guessable files, thus allowing multiple parallel test-path invocations to pass without issues (the idea is to set $TMPDIR early on in the test to some private directory, and then only use the new %T or %V specifier to refer to it).
* man: sort specifier list in systemd.unit(5) alphabeticallyLennart Poettering2018-05-291-28/+28
| | | | | | | | | | | | | | | Usually, we order our settings in our unit files in a logical order, grouping related settings together, and putting more relevant stuff first, instead of following a strictly alphabetical order. For specifiers I think it makes sense to follow an alphabetical order however, since they literally are just characters, and hence I think the concept of alphabetical ordering is much more commanding for them. Also, since specifiers are usually not used in combination, but mostly used indepdently of each other I think it's not that important to group similar ones together. No other changes except the reordering.
* 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: document meaning of age in tmpfiles.d (#8092)Lucas Werkmeister2018-02-051-0/+7
| | | | | | | | | | | This documents how the age of a file is determined, which previously was only alluded to in other parts of the documentation. Fixes #8091. The phrasings of “last modification timestamp” etc. are taken from man:inode(7) (as of man-pages 4.14). The debug messages in tmpfiles.c use different messages (“modify time”), which according to a code comment follow man:stat(1); however, my copy of that manpage (from GNU coreutils 8.29) documents %y as “time of last data modification” instead.
* tmpfiles: make "f" lines behaviour match what the documentation saysLennart Poettering2018-01-241-18/+10
| | | | | | | | | | | | | | | | | | | | CHANGE OF BEHAVIOUR — with this commit "f" line's behaviour is altered to match what the documentation says: if an "argument" string is specified it is written to the file only when the file didn't exist before. Previously, it would be appended to the file each time systemd-tmpfiles was invoked — which is not a particularly useful behaviour as the tool is not idempotent then and the indicated files grow without bounds each time the tool is invoked. I did some spelunking whether this change in behaviour would break things, but afaics nothing relies on the previous O_APPEND behaviour of this line type, hence I think it's relatively safe to make "f" lines work the way the docs say, rather than adding a new modifier for it or so. Triggered by: https://lists.freedesktop.org/archives/systemd-devel/2018-January/040171.html
* tmpfiles: create parent directories if they are missing for more line typesLennart Poettering2018-01-231-0/+7
| | | | | | | | | | | | | | | Currently, we create leading directories implicitly for all lines that create directory or directory-like nodes. With this, we also do the same for a number of other lines: f/F, C, p, L, c/b (that is regular files, pipes, symlinks, device nodes as well as file trees we copy). The leading directories are created with te default access mode of 0755. If something else is desired, users should simply declare appropriate "d" lines. Fixes: #7853
* man: fix example formatting in systemd.presetZbigniew Jędrzejewski-Szmek2018-01-201-1/+1
| | | | | Repeating "example" everywhere was not useful, so remove that and improve the formatting a bit.
* tmpfiles: also add %t/%S/%C/%L specifiersZbigniew Jędrzejewski-Szmek2017-12-061-1/+21
| | | | | | | | | sd_path_home() returns ENXIO when a variable (such as $XDG_RUNTIME_DIR) is not defined. Previously we used ENOKEY for unresolvable specifiers. To avoid having two codes, or translating ENXIO to ENOKEY, I replaced ENOKEY use with ENXIO. v2: - use sd_path_home and change to ENXIO everywhere
* tmpfiles: add --user switchZbigniew Jędrzejewski-Szmek2017-12-061-3/+11
|
* tmpfiles: Add specifiers to allow running as user instanceayekat2017-12-061-0/+15
| | | | | | | | | This commit adds specifiers %U, %u and %h for the user UID, name and home directory, respectively. [zj: drop untrue copy-pasted comments and move the next text to the new "Specifiers" section. Now that #7444 has been merged, also drop the specifier functions.]
* Fail on unknown (alphanumerical) specifiersZbigniew Jędrzejewski-Szmek2017-12-061-0/+1
| | | | | | | | | | | | | | | | | | | | | | | The code intentionally ignored unknown specifiers, treating them as text. This needs to change because otherwise we can never add a new specifier in a backwards compatible way. So just treat an unknown (potential) specifier as an error. In principle this is a break of backwards compatibility, but the previous behaviour was pretty much useless, since the expanded value could change every time we add new specifiers, which we do all the time. As a compromise for backwards compatibility, only fail on alphanumerical characters. This should cover the most cases where an unescaped percent character is used, like size=5% and such, which behave the same as before with this patch. OTOH, this means that we will not be able to use non-alphanumerical specifiers without breaking backwards compatibility again. I think that's an acceptable compromise. v2: - add NEWS entry v3: - only fail on alphanumerical
* man: specifiers are allow for argument field in tmpfilesZbigniew Jędrzejewski-Szmek2017-12-011-45/+52
|
View Lorry Controller Status