From 0a5a8f13b421fb5d4ce0984d8ace8d676252a044 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= Date: Mon, 13 Jan 2020 15:28:25 +0100 Subject: [PATCH 1/2] 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 d98358957b..e1aa656b0f 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. From 744c49e1fef0873320e63bd31839f6ced12ae758 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= Date: Mon, 13 Jan 2020 21:03:15 +0100 Subject: [PATCH 2/2] docs: update link and more dots Apparently unicode ellipsis is too much for github. --- docs/INITRD_INTERFACE.md | 2 +- docs/ROOT_STORAGE_DAEMONS.md | 10 +++++----- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/INITRD_INTERFACE.md b/docs/INITRD_INTERFACE.md index 04b189f89c..8985f2761c 100644 --- a/docs/INITRD_INTERFACE.md +++ b/docs/INITRD_INTERFACE.md @@ -19,7 +19,7 @@ interfaces are currently used by dracut and the ArchLinux initrds. * The initrd should mount `/run/` as a tmpfs and pass it pre-mounted when jumping into the main system when executing systemd. The mount options should - be `mode=755,nodev,nosuid,strictatime` + be `mode=755,nodev,nosuid,strictatime`. * It's highly recommended that the initrd also mounts `/usr/` (if split off) as appropriate and passes it pre-mounted to the main system, to avoid the diff --git a/docs/ROOT_STORAGE_DAEMONS.md b/docs/ROOT_STORAGE_DAEMONS.md index 451034dc76..ff4c771818 100644 --- a/docs/ROOT_STORAGE_DAEMONS.md +++ b/docs/ROOT_STORAGE_DAEMONS.md @@ -90,9 +90,9 @@ kernel threads are excluded too. Thus, a daemon which wants to take advantage of this logic needs to place the following at the top of its main() function: ```c -… +... [0][0] = '@'; -… +... ``` And that's already it. Note that this functionality is only to be used by @@ -116,10 +116,10 @@ otherwise doesn't. Something like this: #include int main(int argc, char *argv[]) { - … + ... if (access("/etc/initrd-release", F_OK) >= 0) argv[0][0] = '@'; - … + ... } ``` @@ -190,4 +190,4 @@ few additional notes for supporting these setups: program consult this blog story: [Socket Activation](http://0pointer.de/blog/projects/socket-activation.html) -* Consider having a look at the [initrd Interface of systemd](http://www.freedesktop.org/wiki/Software/systemd/InitrdInterface) +* Consider having a look at the [initrd Interface of systemd](https://systemd.io/INITRD_INTERFACE/).