chiark / gitweb /
~ianmdlvl / elogind.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: b7e6c03) | patch
journal: allow files with no data whatsoever
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
Sun, 30 Mar 2014 18:20:34 +0000 (14:20 -0400)
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
Wed, 16 Jul 2014 02:23:47 +0000 (22:23 -0400)
commitb3306e9c3c1e036396bc6bf74555eecea3f45ad9
tree48bbd6e1c897540c633d162c15b7fc7e2fe6c6c4tree | snapshot
parentb7e6c03d3bb4e571ad3391862e3f5e4d6bb0cfbbcommit | diff
journal: allow files with no data whatsoever

If a file was opened for writing, and then closed immediately without
actually writing any entries, on subsequent opening, it would be
considered "corrupted". This should be totally fine, and even in
read mode, an empty file can become non-empty later on.
src/journal/journal-file.c diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.