<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - enhance documentation about sd_journal_next after sd_journal_seek_tail"
href="https://bugs.freedesktop.org/show_bug.cgi?id=64614#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - enhance documentation about sd_journal_next after sd_journal_seek_tail"
href="https://bugs.freedesktop.org/show_bug.cgi?id=64614">bug 64614</a>
from <span class="vcard"><a class="email" href="mailto:zbyszek@in.waw.pl" title="Zbigniew Jedrzejewski-Szmek <zbyszek@in.waw.pl>"> <span class="fn">Zbigniew Jedrzejewski-Szmek</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=64614#c1">comment #1</a>)
<span class="quote">> Not that even with improved documentation, it would still be very good to
> have sd_journal_next after sd_journal_seek_tail return an error instead of
> succeeding and moving to a random entry.</span >
You're right, I somehow missed the part about random results...
It would be great if you turned you test program directly into a test that we
can include in systemd. I did something like that with your other program
(<a href="http://cgit.freedesktop.org/systemd/systemd/commit/?id=7a050b54">http://cgit.freedesktop.org/systemd/systemd/commit/?id=7a050b54</a>).
I'm pretty sure that sd_journal_next after sd_journal_seek_tail should return
0.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>