summaryrefslogtreecommitdiffstats
path: root/gnu
diff options
context:
space:
mode:
authorache <ache@FreeBSD.org>1995-04-29 12:22:41 +0000
committerache <ache@FreeBSD.org>1995-04-29 12:22:41 +0000
commit5c6277cb5c8ab30cf474febe760ba6f8383208ed (patch)
tree5cf899a39bd291cdb9b512ccdac27a503ef57852 /gnu
parente9b0cedd67870276aff2ff2a7acd0a27e67241eb (diff)
downloadFreeBSD-src-5c6277cb5c8ab30cf474febe760ba6f8383208ed.zip
FreeBSD-src-5c6277cb5c8ab30cf474febe760ba6f8383208ed.tar.gz
Fix HAVE_SAVED_IDS and HAVE_BROKEN_SETREUID defines
Diffstat (limited to 'gnu')
-rw-r--r--gnu/libexec/uucp/common_sources/policy.h4
1 files changed, 2 insertions, 2 deletions
diff --git a/gnu/libexec/uucp/common_sources/policy.h b/gnu/libexec/uucp/common_sources/policy.h
index 7fd03a2..75b8d21 100644
--- a/gnu/libexec/uucp/common_sources/policy.h
+++ b/gnu/libexec/uucp/common_sources/policy.h
@@ -203,7 +203,7 @@
HAVE_SAVED_SETUID to 1, but your system does not have saved set
user ID, uucp will fail with an error message whenever anybody
other than the uucp user uses it. */
-#define HAVE_SAVED_SETUID 0
+#define HAVE_SAVED_SETUID 1
/* On some systems, such as the DG Aviion and, possibly, the RS/6000,
the setreuid function is broken. It should be possible to use
@@ -213,7 +213,7 @@
set HAVE_BROKEN_SETREUID to 1; if you do not, you will get error
messages from setreuid. Systems on which setreuid exists but is
broken pretty much always have saved setuid. */
-#define HAVE_BROKEN_SETREUID 1
+#define HAVE_BROKEN_SETREUID 0
/* On the 3B2, and possibly other systems, nap takes an argument in
hundredths of a second rather than milliseconds. I don't know of
OpenPOWER on IntegriCloud