tree-wide: the env var is called $XDG_RUNTIME_DIR, not $XDG_RUNTIME_DIRECTORY

diff --git a/docs/TEMPORARY_DIRECTORIES.md b/docs/TEMPORARY_DIRECTORIES.md
index bc9cb7bc455c8f0e180ba288199a77aa8a23ed7a..b0b5da8c06c4dbbe5f12b71d2359341a2eaa471c 100644 (file)
--- a/docs/TEMPORARY_DIRECTORIES.md
+++ b/docs/TEMPORARY_DIRECTORIES.md
@@ -143,7 +143,7 @@ strategies to avoid these issues:
    the sticky bit has a different meaning for them.
 
 6. Don't use `/tmp/` or `/var/tmp/`, but use your own sub-directory under
-   `/run/` or `$XDG_RUNTIME_DIRECTORY` (the former if privileged, the latter if
+   `/run/` or `$XDG_RUNTIME_DIR` (the former if privileged, the latter if
    unprivileged), or `/var/lib/` and `~/.config/` (similar, but with
    persistency and suitable for larger data). The two temporary directories
    `/tmp/` and `/var/tmp/` come with the implicit clean-up semantics described

diff --git a/src/login/pam_systemd.c b/src/login/pam_systemd.c
index 9fc4231b9813b442165a8aee5cebc9a762af2693..a2f0a7373a813df8197ae5cfe82f38ba19d29649 100644 (file)
--- a/src/login/pam_systemd.c
+++ b/src/login/pam_systemd.c
@@ -1569,7 +1569,7 @@ static int setup_environment(
                 /* Also create a per-area subdirectory for $XDG_RUNTIME_DIR, so that each area has their own
                  * set of runtime services. We follow the same directory structure as for $HOME. Note that we
                  * do not define any form of automatic clean-up for the per-aera subdirs beyond the regular
-                 * clean-up of the whole $XDG_RUNTIME_DIRECTORY hierarchy when the user finally logs out. */
+                 * clean-up of the whole $XDG_RUNTIME_DIR hierarchy when the user finally logs out. */
 
                 r = make_area_runtime_directory(handle, ur, runtime_directory, area, &per_area_runtime_directory);
                 if (r != PAM_SUCCESS)