Re: [ovs-dev] [PATCH 2/2] stream-unix: Do not bind a name for client sockets.

2012-03-07 Thread Ben Pfaff
Thanks for looking at these patches. When I rebased these onto current master, I found that there were new test failures due to Python tests added on master in the meantime. Avoiding these (which are genuine bugs) requires a couple of preparatory commits. I'll re-send this as a 4-patch series soo

Re: [ovs-dev] [PATCH 2/2] stream-unix: Do not bind a name for client sockets.

2012-03-07 Thread Ethan Jackson
Looks good, thanks. Ethan On Mon, Feb 27, 2012 at 11:17, Ben Pfaff wrote: > There's no reason for a Unix domain client socket to bind a name.  I don't > know why we've always done that.  Stevens's "Unix Network Programming" > Unix domain socket client example doesn't do a bind. > > Removes the '

[ovs-dev] [PATCH 2/2] stream-unix: Do not bind a name for client sockets.

2012-02-27 Thread Ben Pfaff
There's no reason for a Unix domain client socket to bind a name. I don't know why we've always done that. Stevens's "Unix Network Programming" Unix domain socket client example doesn't do a bind. Removes the 'unlink_path' parameter from new_fd_stream() since it is now always passed as NULL. Si