diff options
author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2014-03-30 14:20:34 -0400 |
---|---|---|
committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2014-07-15 22:23:47 -0400 |
commit | b3306e9c3c1e036396bc6bf74555eecea3f45ad9 (patch) | |
tree | 48bbd6e1c897540c633d162c15b7fc7e2fe6c6c4 /src/python-systemd/pyutil.c | |
parent | b7e6c03d3bb4e571ad3391862e3f5e4d6bb0cfbb (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.
Diffstat (limited to 'src/python-systemd/pyutil.c')
0 files changed, 0 insertions, 0 deletions