[ovs-build] ovs pipe issue on windows

Ben Pfaff blp at ovn.org
Sun Nov 4 15:29:12 UTC 2018


Well, on Unix-like systems it uses Unix domain sockets, and then when we
ported OVS to Windows we still needed the same feature and it made sense
to keep the name, though it's not implemented with Unix domain sockets
there.

On Sun, Nov 04, 2018 at 08:52:42AM +0200, borisusun at gmail.com wrote:
> Indeed it has solved the issue. Just out of curiosity, what’s the purpose of “unix” remote on windows platform.
> 
> Sent from my iPhone
> 
> > On Nov 4, 2018, at 07:20, Ben Pfaff <blp at ovn.org> wrote:
> > 
> >> On Sun, Nov 04, 2018 at 12:31:33AM +0200, Boris Ouretskey wrote:
> >> Hi
> >> 
> >> I am trying to build the ovs for windows according to instructions that
> >> appear here
> >> 
> >> http://docs.openvswitch.org/en/latest/intro/install/windows/
> >> 
> >> Everything went fine (almost make check failed some unitests). However when
> >> I am trying to run the ovsdb-server with the following command line
> >> 
> >> ovsdb-server -vfile:info --remote=unix:db.sock --log-file --pidfile  -v
> > 
> > Probably you want punix: instead of unix:


More information about the build mailing list