diff options
| author | Lennart Poettering <lennart@poettering.net> | 2022-08-25 17:32:28 +0200 |
|---|---|---|
| committer | Luca Boccassi <luca.boccassi@gmail.com> | 2022-08-25 22:27:26 +0100 |
| commit | abd6faae80fa87ecc24a000447b86fc32499809d (patch) | |
| tree | 908abf14e1e4b881b41cec96098acfc733f59ff3 /man/systemd.journal-fields.xml | |
| parent | bf07a1251615629d4fc663b773ef1daf9aad77af (diff) | |
| download | systemd-abd6faae80fa87ecc24a000447b86fc32499809d.tar.gz | |
journal: rename special journal field _SYSTEM_CONTEXT= → _RUNTIME_SCOPE=
Previously the field "_SYSTEM_CONTEXT" knew he values "initrd" + "main". Let's change
this to "_RUNTIME_SCOPE" and "initrd" + "system".
Why? The sysext logic has a very similar concept of "scopes", declaring
whether a sysext image is intended for the initrd or the main system.
Let's thus use the same naming for both.
sysext's extension-release files hence know SYSEXT_SCOPE=initrd|system,
and the journal messages know _RUNTIME_SCOPE=initrd|system, which makes
this reasonably systematic.
Follow-up for: cae8edd93ca2ef90c41cb9b6322b6908d12947b5
(This is not an API break, since no version with this commit has ever
been released.)
Diffstat (limited to 'man/systemd.journal-fields.xml')
| -rw-r--r-- | man/systemd.journal-fields.xml | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/man/systemd.journal-fields.xml b/man/systemd.journal-fields.xml index 320b782992..68581a21cc 100644 --- a/man/systemd.journal-fields.xml +++ b/man/systemd.journal-fields.xml @@ -399,12 +399,12 @@ </listitem> </varlistentry> <varlistentry> - <term><varname>_SYSTEM_CONTEXT=</varname></term> + <term><varname>_RUNTIME_SCOPE=</varname></term> - <listitem><para>A string field that specifies the context in which the message was logged. If - <literal>initrd</literal>, the log message was processed while systemd-journald - was running inside the initrd. If <literal>main</literal>, the log message was generated after - journald switched root to the root filesystem.</para></listitem> + <listitem><para>A string field that specifies the runtime scope in which the message was logged. If + <literal>initrd</literal>, the log message was processed while the system was running inside the + initial RAM disk (initrd). If <literal>system</literal>, the log message was generated after the + system switched execution to the host root filesystem.</para></listitem> </varlistentry> </variablelist> </refsect1> |