[systemd-devel] journalctl --follow broken

[Zbigniew Jędrzejewski-Szmek]

On Tue, Nov 20, 2012 at 06:49:19PM +0100, Lennart Poettering wrote:
> On Thu, 01.11.12 13:03, Zbigniew Jędrzejewski-Szmek (zbyszek at in.waw.pl) wrote:
> 
> > Hi,
> > 
> > today I noticed that journalctl --follow seems to print out much more
> > than 10 lines. Actually, aftern printing 10 lines correctly, it jump
> > to some point in the past:
> > 
> > Logs begin at Sat, 13 Oct 2012 06:13:18 +0000.
> > Nov 01 11:09:26 fedora-15 sshd[29669]: pam_unix(sshd:session): session clos...ek
> > Nov 01 11:09:26 fedora-15 systemd-logind[455]: Removed session 101.
> > Nov 01 11:09:28 fedora-15 python3[29709]: Allowing runtime journal files to ....
> > ESC[1;39m----- Reboot -----ESC[0m
> > Oct 28 12:08:26 fedora-15 systemd[1]: SELinux Got Sender :1.312
> > Oct 28 12:08:26 fedora-15 systemd[1]: GetConnectionSELinuxSecurityContext u...8)
> > ESC[1;39m----- Reboot -----ESC[0m
> > Nov 01 11:09:28 fedora-15 systemd-journal-gatewayd[11055]: Failed to send dat...
> > Nov 01 11:09:51 fedora-15 python3[29729]: Allowing runtime journal files to ....
> > ESC[1;39m----- Reboot -----ESC[0m
> > Oct 28 12:08:26 fedora-15 systemd[1]: SELinux access check scon=unconfined_...ic
> > 
> > Apparently sd_journal_next() makes the jump when at EOF.
> > 
> > I'm too lazy to look into sd_journal_next(), but git bisect points to:
> > 
> >     Author: Lennart Poettering <lennart at poettering.net>
> >     Date:   Fri Sep 21 20:52:23 2012 +0200
> > 
> >     journal: completely rework the mmap cache as I too dumb to actually understand it
> > 
> > Zbyszek
> 
> Hmm, can you use "-o verbose" instead, and check if there really is a
> time jump/seqno jump? (The seqno is the i= bit of the cursor string...)
I can't seem to reproduce it anymore. Probably depends on a specific
set of logs, which I didn't think to copy.

Zbyszek