From 5454da3bcaa383f5b47984283f11f010d3d2b73e Mon Sep 17 00:00:00 2001 From: Greg Hudson Date: Wed, 1 May 2013 13:07:36 -0400 Subject: Don't use portmapper in RPC tests On many Linux systems, due to what is arguably a bug in rpcbind, the portmapper doesn't allow service registration from non-root processes. This causes the RPC tests to be frequently skipped. Modify the tests so that they don't need the portmapper, by grabbing the port number from the server process and passing it to the client. --- doc/build/doing_build.rst | 3 --- 1 file changed, 3 deletions(-) (limited to 'doc') diff --git a/doc/build/doing_build.rst b/doc/build/doing_build.rst index bc438c849e..3c686cc716 100644 --- a/doc/build/doing_build.rst +++ b/doc/build/doing_build.rst @@ -149,9 +149,6 @@ However, there are several prerequisites that must be satisfied first: **-**\ **-disable-rpath**, which renders the build tree less suitable for installation, but allows testing without interference from previously installed libraries. -* In order to test the RPC layer, the local system has to be running - the portmap daemon and it has to be listening to the regular network - interface (not just localhost). There are additional regression tests available, which are not run by ``make check``. These tests require manual setup and teardown of -- cgit