tl;dr Go's Sendmsg always sends a "dummy byte" even when you are only
sending OOB data. This breaks a protocol I want to talk to:
systemd-journal. See attached patch for a "fix".
While working on go-systemd David found that Go syscall.Sendmsg was
always sending one byte of data when we only wanted to send out of
band data (a file descriptor). The attached patch "fixes" the problem
for us but also breaks the tests.
This is the line of code in systemd-journal that rejects messages with
the dummy byte:
Instead of fixing everything up I wanted to understand _why_ this
dummy byte is being sent first. The code seems to have been there
since the initial commit of the syscall_linux.go.
So, why was does this dummy byte exist? Are there other platforms that
require this byte?
If I fixup all of the tests and the poller is this patch mergeable?
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
For more options, visit https://groups.google.com/groups/opt_out.