shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-12-22 17:35:35 +03:00
Code

tree-wide: drop all references to "journalctl --new-id128"

Browse Source 
Let's advertise "systemd-id128 new" instead.
This commit is contained in:
Lennart Poettering 2018-10-02 16:43:54 +02:00
parent 19a073db9b
commit b9d016d684
4 changed files with 12 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
man/sd-id128.xml
View File

@ -141,8 +141,8 @@ int main(int argc, char **argv) {
}</programlisting>
<para>Note that new, randomized IDs may be generated with
<citerefentry><refentrytitle>journalctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>'s
<option>--new-id128</option> option.</para>
<citerefentry><refentrytitle>systemd-id128</refentrytitle><manvolnum>1</manvolnum></citerefentry>'s
<command>new</command> command.</para>
</refsect1>
<xi:include href="libsystemd-pkgconfig.xml" />

6
man/sd_id128_randomize.xml
View File

@ -52,9 +52,9 @@
type, see
<citerefentry><refentrytitle>sd-id128</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para>
<para><citerefentry><refentrytitle>journalctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>'s
<option>--new-id128</option> option may be used as a command line
front-end for <function>sd_id128_randomize()</function>.</para>
<para><citerefentry><refentrytitle>systemd-id128</refentrytitle><manvolnum>1</manvolnum></citerefentry>'s
<command>new</command> command may be used as a command line front-end for
<function>sd_id128_randomize()</function>.</para>
</refsect1>
<refsect1>

12
man/systemd.journal-fields.xml
View File

@ -56,14 +56,10 @@
<varlistentry>
<term><varname>MESSAGE_ID=</varname></term>
<listitem>
<para>A 128-bit message identifier ID for recognizing
certain message types, if this is desirable. This should
contain a 128-bit ID formatted as a lower-case hexadecimal
string, without any separating dashes or suchlike. This is
recommended to be a UUID-compatible ID, but this is not
enforced, and formatted differently. Developers can generate
a new ID for this purpose with <command>journalctl
<option>--new-id128</option></command>.
<para>A 128-bit message identifier ID for recognizing certain message types, if this is desirable. This
should contain a 128-bit ID formatted as a lower-case hexadecimal string, without any separating dashes or
suchlike. This is recommended to be a UUID-compatible ID, but this is not enforced, and formatted
differently. Developers can generate a new ID for this purpose with <command>systemd-id128 new</command>.
</para>
</listitem>
</varlistentry>

8
src/systemd/sd-messages.h
View File

@ -23,12 +23,10 @@
_SD_BEGIN_DECLARATIONS;
/* Hey! If you add a new message here, you *must* also update the
* message catalog with an appropriate explanation */
/* Hey! If you add a new message here, you *must* also update the message catalog with an appropriate explanation */
/* And if you add a new ID here, make sure to generate a random one
* with journalctl --new-id128. Do not use any other IDs, and do not
* count them up manually. */
/* And if you add a new ID here, make sure to generate a random one with "systemd-id128 new". Do not use any other IDs,
* and do not count them up manually. */
#define SD_MESSAGE_JOURNAL_START SD_ID128_MAKE(f7,73,79,a8,49,0b,40,8b,be,5f,69,40,50,5a,77,7b)
#define SD_MESSAGE_JOURNAL_START_STR SD_ID128_MAKE_STR(f7,73,79,a8,49,0b,40,8b,be,5f,69,40,50,5a,77,7b)