tree 349a91fe8a76d8f54447774b6cce032a06e4d651
parent f6150403cc5ff5fc69d5f9dca4d305c4aaac933e
author Vernon Mauery <vernon.mauery@linux.intel.com> 1545177426 -0800
committer Vernon Mauery <vernon.mauery@linux.intel.com> 1547060858 +0000

bmcweb: remove boost::asio::local::stream_protocol::endpoint hack

With the obmc-console-server binding to the correct socket, this is not
needed.

Abstract unix sockets start with the nul-charater, but are not nul
terminated. In fact, the nul-character has no meaning in the path.
According to the man page unix(7),

abstract:  an abstract socket address is distinguished (from a pathname
           socket) by the fact that sun_path[0] is a null byte ('\0').
           The socket's address in  this  namespace is  given by the
           additional bytes in sun_path that are covered by the
           specified length of the address structure.  (Null bytes in
           the name have no special significance.)

This means that when calling bind/connect, the size of the sockaddr
structure is not sizeof(sockaddr_un), it is sizeof(sockaddr_un) -
sizeof(sun_path) + (path_len)

Change-Id: I2b19d0b9aa8e8ded9162890503c46cad95a6c7b6
Signed-off-by: Vernon Mauery <vernon.mauery@linux.intel.com>