I have a program which starts

osqueryd

by using

--extensions-socket=$HOME/osqueryd/osquery.em

, where the actual path is constructed in a crossplatform way (using

go

's

filepath.Join

function)

Pipes on Windows look more like

\\.\PIPE\yourthinghere

. see https://en.wikipedia.org/wiki/Named_pipe#In_Windows

Right, I remember something like this, thank you. This means that in my program, I probably need to name the socket differently depending on the platform

I’ve also run into issues on windows, where sometims there’s a stale pipe and I can’t make a new one