Hi Moritz--
On 02/16/2011 10:42 AM, Moritz Muehlenhoff wrote:
> Our buildsystem uses largish file names, which exposed a bug in the test
> suite:
>
> tests/basic tries to create a socket:
>
> socat EXEC:"/usr/sbin/sshd -f ${SSHD_CONFIG} -i -D -e"
> "UNIX-LISTEN:${SOCKET}" 2> "$TEMPDIR"/sshd.log &
>
> Since the maximum socket name length is 108 chars, it fails when build in
> large directory. You can reproduce by building in
> ~/1111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111
Thanks for the report! We're aware of this limitation: #573902 is
marked "affects monkeysphere".
http://bugs.debian.org/573902
I'm not sure how to resolve the problem reliably, though, since the
socket name length limitation appears to come from
/usr/include/sys/un.h and i don't know if that's fixable or not.
Do you have any suggestions, Moritz? I suppose we could make the test
suite fail earlier, or try to force the creation of the socket someplace
else in the filesystem (e.g. test if socat fails with the given error,
and if so try again with (mktemp -d /tmp/mstest.XXXXXXXXX). But we have
no guarantees that this is even possible (so it might still fail), and
it means a more convoluted cleanup process for the test suite.
I'm open to alternate ideas.
--dkg
signature.asc
Description: OpenPGP digital signature
