[mod_gnutls-devel] New Release: mod_gnutls 0.7.1
thomas2.klute at uni-dortmund.de
Tue Oct 20 15:54:09 CEST 2015
Am 20.10.2015 um 04:49 schrieb Daniel Kahn Gillmor:
> Thanks for these fixes! I'm noticing that now that we're looking for
> apache2 or httpd in the $PATH for the test suite, that's not working
> when testing as a non-privileged user on debian, since apache2 is in
> /usr/sbin, but the normal non-privileged user doesn't have /sbin or
> /usr/sbin in their $PATH.
Appending /usr/sbin to the search path seems reasonable, I've pushed it
to master (rev 83b39016614370843a98b1b85d4fe5517e4bb7c6, ). For the
release version you can just pass an extended path to ./configure:
AC_PATH_PROGS stores the absolute path, so there's no need to change the
PATH for the rest of the build.
> However, i'm now seeing apache hanging during the tests -- it has port
> 9932 open, and is listening, but gnutls-cli hangs in TCP_SYN state when
> connecting to it.
> any ideas what i should try for debugging it?
That is strange. Aside from checking logs (startup messages now go to
the individual test log, e.g. test/test-00_basic.bash.log, access and
error logs to test/logs/ as before), two things come to mind:
* Are test TEST_HOST and TEST_IP correct for your system? Debian's
default /etc/hosts file configures "localhost" as IPv4 only, so I have
to pass either TEST_HOST="ip6-localhost" or TEST_IP="127.0.0.1" to
./configure, otherwise host name and IP don't match.
* If you want to start the Apache process manually (e.g. with a
Debugger), run "make show-test-env" in the test/ directory, which will
dump the content of AM_TESTS_ENVIRONMENT to stdout, so you can easily
provide the same environment as the test suite.
More information about the mod_gnutls-devel