From: Steven Hum <sdothum@gmail.com>
To: voidlinux <voidlinux@googlegroups.com>
Subject: [void musl] mkfifo buffer exhibiting unexpected behaviour
Date: Wed, 16 Jan 2019 23:14:05 -0800 (PST) [thread overview]
Message-ID: <76d8f6be-6ddb-4bb6-81f8-3a29482317b0@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1434 bytes --]
I posted this on the musl mailing list (after being redirected on the
voidlinux reddit forum):
> Running this simple test using clock from sutils to produce a repeating
one second interval input stream..
>
> mkfifo fifo
> clock -i 1 -sf "T> stream one" >fifo &
> clock -i 1 -sf "D> stream two" >fifo &
> cat fifo
>
> on void musl only the second fifo input stream is displayed.
> on void glibc, both input streams are displayed interleaved as expected.
>
> Are fifo buffers handled differently under musl?
The reply was:
*No, aside from possible stdio buffering it's entirely a kernel matter.*
I looked up the sutils source and see it's flushing after each output,
and tried it on an Alpine-based box here (with musl) and could not
reproduce what you're seeing. Both outputs are visible and roughly
interleaved (although their order sometimes swaps with scheduling, of
course).
--
So... is this a bug within void musl?
Regards,
Steven
--
You received this message because you are subscribed to the Google Groups "voidlinux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to voidlinux+unsubscribe@googlegroups.com.
To post to this group, send email to voidlinux@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/voidlinux/76d8f6be-6ddb-4bb6-81f8-3a29482317b0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 2307 bytes --]
next reply other threads:[~2019-01-17 7:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 7:14 Steven Hum [this message]
2019-01-17 12:28 ` mail
2019-01-17 14:12 ` Steven Hum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=76d8f6be-6ddb-4bb6-81f8-3a29482317b0@googlegroups.com \
--to=sdothum@gmail.com \
--cc=voidlinux@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).