Re: daemontools tai64n is unbuffered, s6-tai64n is fully buffered

On 20/10/2015 02:16, Buck Evan wrote: My canonical slowly-printing example is: yes hello world | pv -qL 10 | tai64n Under daemontools classic you'll see the output gradually appear character by character, with timestamps. Under s6, this seems to hang and I ctrl-c it. I'm sure if I waited

Re: daemontools tai64n is unbuffered, s6-tai64n is fully buffered

Thanks! Trying now... After bumping to your latest releases, s6-tai64n now shows line-buffered behavior. Close enough! On Tue, Oct 20, 2015 at 1:54 AM, Laurent Bercot wrote: > On 20/10/2015 02:16, Buck Evan wrote: > >> My canonical slowly-printing example is: >> >>

Re: daemontools tai64n is unbuffered, s6-tai64n is fully buffered

Is it expected that it's line-buffered? On Tue, Oct 20, 2015 at 2:35 PM, Laurent Bercot wrote: > On 20/10/2015 23:31, Buck Evan wrote: > >> Confirmed fixed. Can I get a micro release? I'll pin myself to that one >> for >> the moment. >> > > Find me another bug and I'll

Re: daemontools tai64n is unbuffered, s6-tai64n is fully buffered

On 20/10/2015 23:36, Buck Evan wrote: Is it expected that it's line-buffered? It's not line-buffered. It's optimally buffered, i.e. the buffer is flushed whenever it's full (obviously) or whenever the loop goes back to reading with a chance of blocking. When you test with a loop around echo,

Re: daemontools tai64n is unbuffered, s6-tai64n is fully buffered

There's no loop around echo: $ yes oh, hi! | pv -qL 10 | tai64n | s6-tai64nlocal 2015-10-20 09:47:02.681071500 oh, hi! 2015-10-20 09:47:03.493098500 oh, hi! 2015-10-20 09:47:04.304479500 oh, hi! ^C yes oh, hi! | pv -qL 10 | tai64n | tai64nlocal 2015-10-20 09:47:44.813611500 oh, hi!

Re: daemontools tai64n is unbuffered, s6-tai64n is fully buffered

On Tue, Oct 20, 2015 at 5:01 PM, Laurent Bercot wrote: > On 21/10/2015 01:05, Buck Evan wrote: > >> This prints slowly enough that I can *see* that tai64nlocal is printing >> each character separately, but s6-tainlocal is printing per-line. >> > > Ah, I understand.

daemontools tai64n is unbuffered, s6-tai64n is fully buffered

Is this an intentional difference? It makes looking at the log output much less useful, since the output is ~2K behind on average, which in terms of time can be hours or even unbounded.