Kilian Ciuffolo

thanks for giving little more context. I will run a test myself with high throughput and see if I can manage to reproduce it. - Are you guys running latest...

This shouldn't be happening. Are you 100% sure you are not writing the two files with the same content? OS / Node version / rtail version?

Yeah I think something changed somewhere in the deps tree or in the browser API because it used to work. I am def need to look into it. Thanks for...

v0.3.0 will turn timestamp parsing by default and we will implement timestamp parsing on our own as new use cases will come in. The library that we are using right...

@kbariotis thank for contributing and taking the time to leave a message :) rtail ui already pauses the socket on scroll, is that what you are suggesting ?

@thelinuxlich did you figure what's wrong?

Oh cool, but I still want to know if the issue was your particular use case or systemd or in rtail, if it's the second I want to fix it.

what happens if you do `> file.log` ? what is the exact command you are trying to launch ?

@astanciu thanks for reporting this. I am on it.

@rictorres it depends on stdin back-pressure. What happens with all clients off?