summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel J Walsh <dwalsh@redhat.com>2022-03-28 09:08:00 -0400
committerGitHub <noreply@github.com>2022-03-28 09:08:00 -0400
commit7df6849f167a4d81feba6f61e9f5bbb084adce62 (patch)
tree80fc9838197fc9af0f7bbf60a4cda3320fea5b1c
parent0ebf0bc56091d305ac064c59e20289d47bf56437 (diff)
parentd4bf6b4d78837ef2c542dc6a487184ffb5a5e119 (diff)
downloadpodman-7df6849f167a4d81feba6f61e9f5bbb084adce62.tar.gz
podman-7df6849f167a4d81feba6f61e9f5bbb084adce62.tar.bz2
podman-7df6849f167a4d81feba6f61e9f5bbb084adce62.zip
Merge pull request #13648 from adamaze/main
[CI:DOCS] clarifying "loginctl enable-linger" section in doc
-rw-r--r--docs/source/markdown/podman-generate-systemd.1.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/source/markdown/podman-generate-systemd.1.md b/docs/source/markdown/podman-generate-systemd.1.md
index 32d5d2bc4..650ffa52f 100644
--- a/docs/source/markdown/podman-generate-systemd.1.md
+++ b/docs/source/markdown/podman-generate-systemd.1.md
@@ -224,7 +224,7 @@ To run the user services placed in `$HOME/.config/systemd/user` on first login o
```
$ systemctl --user enable <.service>
```
-The systemd user instance is killed after the last session for the user is closed. The systemd user instance can be kept running ever after the user logs out by enabling `lingering` using
+The systemd user instance is killed after the last session for the user is closed. The systemd user instance can be started at boot and kept running even after the user logs out by enabling `lingering` using
```
$ loginctl enable-linger <username>