From 92fba83e3a23ce7778a1bde67d277fdc97ab39f9 Mon Sep 17 00:00:00 2001 From: Zbigniew Jędrzejewski-Szmek Date: Sat, 22 Jun 2013 20:04:08 -0400 Subject: journal-verify: allow unlinked data entries Sometimes an entry is not successfully written, and we end up with data items which are "unlinked", not connected to, and not used by any entry. This will usually happen when we write to write a core dump, and the initial small data fields are written successfully, but the huge COREDUMP= field is not written. This situation is hard to avoid, but the results are mostly harmless. Thus only warn about unused data items. Also, be more verbose about why journal files failed verification. This should help diagnose journal failure modes without resorting to a hexadecimal editor. https://bugs.freedesktop.org/show_bug.cgi?id=65235 (esp. see system.journal attached to the bug report). --- man/udev.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'man/udev.xml') diff --git a/man/udev.xml b/man/udev.xml index e253a0677a..964aeda802 100644 --- a/man/udev.xml +++ b/man/udev.xml @@ -317,7 +317,7 @@ The name of a symlink targeting the node. Every matching rule adds this value to the list of symlinks to be created. The set of characters to name a symlink is limited. Allowed - characters are [0-9A-Za-z#+-.:=@_/], valid utf8 character sequences, + characters are [0-9A-Za-z#+-.:=@_/], valid UTF-8 character sequences, and "\x00" hex encoding. All other characters are replaced by a '_' character. Multiple symlinks may be specified by separating the names by the -- cgit v1.2.3-54-g00ecf