Chris Murphy writes:
> Yeah I don't know any details about this hook; but basically
> systemd-journald is the single source for logging now, but it provides
> a socket for rsyslog (and other conventional loggers that have been
> updated) can grab the stream and do their own thing like they have i
On Tue, Feb 10, 2015 at 5:22 PM, Wolfgang S. Rupprecht
wrote:
>
> Chris Murphy writes:
>> Is this delayed behavior reproducible in a shell running journalctl -f
>> ? Or only happens with the script log?
>
> I guess I need to get off my duff and run that test.
>
>> If you aren't using rsyslog, I w
Chris Murphy writes:
> Is this delayed behavior reproducible in a shell running journalctl -f
> ? Or only happens with the script log?
I guess I need to get off my duff and run that test.
> If you aren't using rsyslog, I wonder if you can use the single socket
> designed for this instead, if th
Is this delayed behavior reproducible in a shell running journalctl -f ? Or
only happens with the script log? If you do both at the same time, i.e. one
instance of journalctl -f running in a terminal window, another instance
executes within your Perl script, once the delay is happening does it
appe
Chris Murphy writes:
> On Mon, Feb 9, 2015 at 11:59 PM, Wolfgang S. Rupprecht
> wrote:
>>
>> Is journalctl in the tail -f mode called "follow" supposed to be
>> realtime? I'm seeing it more or less output log lines in realtime for
>> many hours and then eventually it falls behind with half an
On Mon, Feb 9, 2015 at 11:59 PM, Wolfgang S. Rupprecht
wrote:
>
> Is journalctl in the tail -f mode called "follow" supposed to be
> realtime? I'm seeing it more or less output log lines in realtime for
> many hours and then eventually it falls behind with half an hour or one
> hour delay.
>
> Th
