forked from lix-project/lix
unix-domain-socket.cc: add comment explaining why bindConnectProcHelper
We reviewed this code a while ago, and we neglected to get a comment in
saying why it's Like This at the time. Let's fix that, since it is code
that looks very absurd at first glance.
Change-Id: Ib67b49605ef9ef1c84ecda1db16be74fc9105398
This commit is contained in:
parent
562ff516ab
commit
26b3a1b9ce
|
@ -37,6 +37,17 @@ AutoCloseFD createUnixDomainSocket(const Path & path, mode_t mode)
|
||||||
return fdSocket;
|
return fdSocket;
|
||||||
}
|
}
|
||||||
|
|
||||||
|
/**
|
||||||
|
* Workaround for the max length of Unix socket names being between 102
|
||||||
|
* (darwin) and 108 (Linux), which is extremely short. This limitation is
|
||||||
|
* caused by historical restrictions on sizeof(struct sockaddr):
|
||||||
|
* https://unix.stackexchange.com/a/367012.
|
||||||
|
*
|
||||||
|
* Our solution here is to start a process inheriting the socket, chdir into
|
||||||
|
* the directory of the socket, then connect with just the filename. This is
|
||||||
|
* rather silly but it works around working directory being process-wide state,
|
||||||
|
* and is as clearly sound as possible.
|
||||||
|
*/
|
||||||
static void bindConnectProcHelper(
|
static void bindConnectProcHelper(
|
||||||
std::string_view operationName, auto && operation,
|
std::string_view operationName, auto && operation,
|
||||||
int fd, const std::string & path)
|
int fd, const std::string & path)
|
||||||
|
|
Loading…
Reference in a new issue