Changeset b21bf4f in mod_gnutls for test/README


Ignore:
Timestamp:
Jan 28, 2016, 2:46:58 PM (4 years ago)
Author:
Thomas Klute <thomas2.klute@…>
Branches:
debian/master, debian/stretch-backports, jessie-backports, master, upstream
Children:
4d2d182
Parents:
29d3311
git-author:
Thomas Klute <thomas2.klute@…> (01/28/16 14:39:10)
git-committer:
Thomas Klute <thomas2.klute@…> (01/28/16 14:46:58)
Message:

configure: Check if creating namespaces is possible

Some Linux distributions (I've observed this on Debian) restrict
unprivileged users' ability to create namespaces, so checking just
whether the "unshare" command is available is not enough: If it is but
the user building mod_gnutls does not have the necessary permissions,
test cases will fail when trying to create their namespaces. Add a
check that tries to actually create a namespace and disable namespace
isolation of tests if it fails.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • test/README

    r29d3311 rb21bf4f  
    8888backend, and there is no technical requirement to use "runtests".
    8989
    90 By default (if "unshare" is available and --disable-test-namespaces
    91 has NOT been passed to configure), each test case is run inside its
    92 own network namespace. This avoids address and port conflicts with
     90By default (if "unshare" is available and has the permissions required
     91to create network and user namespaces), each test case is run inside
     92its own network namespace. This avoids address and port conflicts with
    9393other tests as well has the host system.
    9494
     
    127127The first two of these issues are avoided when the tests are isolated
    128128using network namespaces, which is the default (see "Implementation"
    129 above).
     129above). The ./configure script tries to detect if namespaces can be
     130used (some Linux distributions disable them for unprivileged
     131users). If this detection returns a false positive or you do not want
     132to use namespace isolation for some other reason, you can run
     133configure with the --disable-test-namespaces option.
    130134
    131135In some situations you may want to see the exact environment as
Note: See TracChangeset for help on using the changeset viewer.