http://bugzilla.spamassassin.org/show_bug.cgi?id=4380
------- Additional Comments From [EMAIL PROTECTED] 2005-06-06 10:10 ------- Subject: Re: spamd on FreeBSD fails to support UNIX domain sockets -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >The one in brackets is the output from $server->hostpath() (ie. the internal >representation of the socket in IO::Socket::UNIX) which I added in r180306. >There you see that something (I guess sockaddr_un()) truncates the path. > >The second error also sounds like it actually creates a socket but with the >wrong name. > >I'll add a check for hostpath() ne $path which will make spamd fail with an >error better to understand. > You're finding basically what I've found. Something is truncating the path. I started some simple searches last night to find a reference in the FreeBSD or OpenBSD code that would confirm this but couldn't. I was certainly able to recreate the issue outside of the buildbot environment by moving the tree to a really long pathname and running make test from there. >That won't help for the buildbots though, they will still fail. What shall we >do? Shall we just move the build directory to /tmp? > This is actually what I'm contemplating, instead of putting the socket in the t/log directory we could make something that will not conflict in /tmp, maybe only on error when trying to create a socket in the t/log dir. Michael -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD8DBQFCpINkG4km+uS4gOIRArmEAJ0Qr13JqdwxGh7B8z3rIyzSulk4kACbBlRX 0amlUuSt47QzC0oC7uzqVAU= =4A6F -----END PGP SIGNATURE----- ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
