From 0a5a8f13b421fb5d4ce0984d8ace8d676252a044 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= Date: Mon, 13 Jan 2020 15:28:25 +0100 Subject: [PATCH] docs: say that journalctl --flush/--sync also require journald https://github.com/systemd/systemd/pull/14549#pullrequestreview-341758182 --- docs/PORTABILITY_AND_STABILITY.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/PORTABILITY_AND_STABILITY.md b/docs/PORTABILITY_AND_STABILITY.md index d98358957b1..e1aa656b0f5 100644 --- a/docs/PORTABILITY_AND_STABILITY.md +++ b/docs/PORTABILITY_AND_STABILITY.md @@ -155,6 +155,8 @@ without communicating with the `systemd` process: Many other programs support operation without the system manager except when the specific functionality requires such communication. For example `journalctl` operates almost independently, but will query the boot id when -`--boot` option is used. `systemd-journal-remote`, `systemd-journal-upload`, -`systemd-journal-gatewayd`, `coredumpctl`, `busctl`, `systemctl --root` also -fall into this category. +`--boot` option is used; it also requires `systemd-journald` (and thus +`systemd`) to be running for options like `--flush` and `--sync`. +`systemd-journal-remote`, `systemd-journal-upload`, `systemd-journal-gatewayd`, +`coredumpctl`, `busctl`, `systemctl --root` also fall into this category of +mostly-independent programs. -- 2.47.3