diff options
author | Jim Meyering <jim@meyering.net> | 2003-07-16 07:59:05 +0000 |
---|---|---|
committer | Jim Meyering <jim@meyering.net> | 2003-07-16 07:59:05 +0000 |
commit | fd35a8b08166af5b9b16bd1c83d4f7ae881e55c4 (patch) | |
tree | ace9a7db9d77e067a0fbe1891253e0be26b7e489 | |
parent | aad28eb267f400ae70a8ad02f4aea4aeec0a2080 (diff) | |
download | coreutils-fd35a8b08166af5b9b16bd1c83d4f7ae881e55c4.tar.xz |
Update section on testing as `root'.
Suggestion from Paul Jarc.
-rw-r--r-- | README | 12 |
1 files changed, 8 insertions, 4 deletions
@@ -73,10 +73,14 @@ Here is one possible patch to correct the problem. -#ifndef __STDC_32_MODE__ +#ifndef __LP64__ -On some systems, some of the tests fail when run as root. All failures -I've seen appear to be due to problems in the testing framework, not -in the tools themselves. I'll address that for the next release by -using a program like setuidgid (see the comment in TODO). +If you run the tests as root, note that a few of them create files +and/or run programs as a non-root user, `nobody' by default. +If you want to use some other non-root username, specify it via +the NON_ROOT_USERNAME environment variable. +If you can run the tests as root, please do so and report any +problems. We get much less test coverage in that mode, and it's +arguably more important that these tools work well when run by +root than when run by unprivileged users. *************************************** |