summaryrefslogtreecommitdiff
path: root/FAQ
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>1998-01-31 12:11:10 +0000
committerUlrich Drepper <drepper@redhat.com>1998-01-31 12:11:10 +0000
commit4d06461a76587c80359f6db5e1c6e4f4641d2663 (patch)
tree50f8b63101860d3e414a4b1276e49c8e26469453 /FAQ
parentd67281a7eac124e2f1b498c377dde3432f711039 (diff)
Update.
1998-01-31 20:52 Ulrich Drepper <drepper@cygnus.com> * nscd/grpcache.c (cache_grpinit): Let calloc do the multiplication. * nscd/pwdcache.c (cache_pwdinit): Use thread attribute to detach thread and no pthread_detach. * nscd/nscd.c: Rewrite to use argp instead of getopt. * config.make.in: Likewise.
Diffstat (limited to 'FAQ')
-rw-r--r--FAQ32
1 files changed, 22 insertions, 10 deletions
diff --git a/FAQ b/FAQ
index f8d462c559..a54db102da 100644
--- a/FAQ
+++ b/FAQ
@@ -60,15 +60,17 @@ please let me know.
were used on my Linux libc5 based system. Why?
2.10. I have set up /etc/nis.conf, and the Linux libc 5 with NYS
works great. But the glibc NIS+ doesn't seem to work.
-2.11. After installing glibc name resolving doesn't work properly.
-2.12. I have /usr/include/net and /usr/include/scsi as symlinks
+2.11. I have killed ypbind to stop using NIS, but glibc will
+ continue using NIS.
+2.12. After installing glibc name resolving doesn't work properly.
+2.13. I have /usr/include/net and /usr/include/scsi as symlinks
into my Linux source tree. Is that wrong?
-2.13. Programs like `logname', `top', `uptime' `users', `w' and
+2.14. Programs like `logname', `top', `uptime' `users', `w' and
`who', show incorrect information about the (number of)
users on my system. Why?
-2.14. After upgrading to glibc 2.1 with symbol versioning I get
+2.15. After upgrading to glibc 2.1 with symbol versioning I get
errors about undefined symbols. What went wrong?
-2.15. When I start the program XXX after upgrading the library
+2.16. When I start the program XXX after upgrading the library
I get
XXX: Symbol `_sys_errlist' has different size in shared
object, consider re-linking
@@ -638,14 +640,24 @@ it with nisinit from the nis-tools package (available at
http://www-vt.uni-paderborn.de/~kukuk/linux/nisplus.html).
-2.11. After installing glibc name resolving doesn't work properly.
+2.11. I have killed ypbind to stop using NIS, but glibc will
+ continue using NIS.
+
+{TK} For faster NIS lookups, glibc uses the /var/yp/binding/ files
+from ypbind. ypbind 3.3 and older versions don't always remove these
+files, so glibc will use them furthermore. Other BSD versions seem to
+work correct. Until ypbind 3.4 is released, you can find a patch at
+ftp://ftp.kernel.org/pub/linux/utils/net/NIS/ypbind-3.3-glibc2.diff.
+
+
+2.12. After installing glibc name resolving doesn't work properly.
{AJ} You probably should read the manual section describing
nsswitch.conf (just type `info libc "NSS Configuration File"').
The NSS configuration file is usually the culprit.
-2.12. I have /usr/include/net and /usr/include/scsi as symlinks
+2.13. I have /usr/include/net and /usr/include/scsi as symlinks
into my Linux source tree. Is that wrong?
{PB} This was necessary for libc5, but is not correct when using
@@ -656,14 +668,14 @@ any symlink that you have in place before you install glibc. However,
/usr/include/asm and /usr/include/linux should remain as they were.
-2.13. Programs like `logname', `top', `uptime' `users', `w' and
+2.14. Programs like `logname', `top', `uptime' `users', `w' and
`who', show incorrect information about the (number of)
users on my system. Why?
{MK} See question 3.2.
-2.14. After upgrading to glibc 2.1 with symbol versioning I get
+2.15. After upgrading to glibc 2.1 with symbol versioning I get
errors about undefined symbols. What went wrong?
{AJ} The problem is caused either by wrong program code or tools. In
@@ -677,7 +689,7 @@ the price you might have to pay once for quite a number of advantages
with symbol versioning.
-2.15. When I start the program XXX after upgrading the library
+2.16. When I start the program XXX after upgrading the library
I get
XXX: Symbol `_sys_errlist' has different size in shared
object, consider re-linking