https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7986
Sidney Markowitz <sid...@sidney.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sid...@sidney.com
--- Comment #1 from Sidney Markowitz <sid...@sidney.com> ---
According to implications of these two answers to a question on stackoverflow
https://stackoverflow.com/a/783145 and https://stackoverflow.com/a/783194
Unix domain sockets have to look like a valid file name in a directory that
exists. Also, whatever user uses the socket has to have appropriate permissions
for the directory. But I don't see why the socket path can't start with /tmp
instead of the current directory to ensure that the pathname length never
exceeds the limit.
Anyone with more experience with Unix domain sockets who can say if that seems
like a reasonable fix? Can we count on there being a writeable /tmp directory?
It would be more reliable to get the temp file directory name from File::Spec,
but while running
perl -MFile::Spec -e 'print File::Spec->tmpdir();'
in Ubuntu prints /tmp, on my Mac I get the disgustingly long
/var/folders/j_/l6_c445j0v7gy0dw7y35jq240000gn/T
even though there is an available /tmp directory in macOS.
--
You are receiving this mail because:
You are the assignee for the bug.
