libc 4.6.27 bug

libc 4.6.27 bug

Post by Richard Shephe » Wed, 15 Feb 1995 09:11:46



I just upgraded from libc.so.4.5.26 to 4.6.27 and rebooted just
to make sure everything was happy and on booting I noticed that
it couldn't get my nfs mounts connected.  On further investigation
it appears that nslookup and any network stuff is a bit stuffed now!

i.e. nslookup works on full names and machines within my immediate
domain (math.waikato.ac.nz) but not on machines within the larger
domain of waikato.ac.nz which it used to be able to do.  I renamed
libc.so.4.6.27 to something unrecognisable by ldconfig and made
the old libc (libc.so.4.5.26) be pointed to by libc.so.4 and
rebooted and it now resolves addresses properly (as before)
so that must mean it's a bug in libc.so.4.6.27 right?

Anyone else noticed this?

Is it already well known?

--

8<--------------------------->8

Richard Shepherd.


(boring ~/.signature eh?)

 
 
 

libc 4.6.27 bug

Post by A O V Le Bla » Fri, 17 Feb 1995 00:58:42



>I just upgraded from libc.so.4.5.26 to 4.6.27 ...
>it appears that nslookup and any network stuff is a bit stuffed now!
>i.e. nslookup works on full names and machines within my immediate
>domain (math.waikato.ac.nz) but not on machines within the larger
>domain of waikato.ac.nz which it used to be able to do.

Have you set up a 'search' line in your resolv.conf?  Instead of
'domain math.waikato.ac.nz' you can have
'search math.waikato.ac.nz waikato.ac.nz ac.nz nz' for example.
I think it actually works with both kinds of lines, but some of
the documentation with the source suggests that you should not
have both.  H J Lu mentions the search line in one of the documents
that he put out with one of the libc releases, release.libc-4.6.27.

     -- Owen


 
 
 

libc 4.6.27 bug

Post by Peter Dri » Fri, 17 Feb 1995 16:47:26



: Have you set up a 'search' line in your resolv.conf?  Instead of
: 'domain math.waikato.ac.nz' you can have
: 'search math.waikato.ac.nz waikato.ac.nz ac.nz nz' for example.
: I think it actually works with both kinds of lines, but some of
: the documentation with the source suggests that you should not
: have both.  H J Lu mentions the search line in one of the documents
: that he put out with one of the libc releases, release.libc-4.6.27.

on the subject of docs... where are the documents for files like this one?  
I have never seen a doc/man page/ or anything on resolv.conf.  And a lot
of other files for that matter.

Peter Drier

 
 
 

libc 4.6.27 bug

Post by Bernd Eckenfe » Sun, 19 Feb 1995 13:23:00



> on the subject of docs... where are the documents for files like this one?  
> I have never seen a doc/man page/ or anything on resolv.conf.  And a lot
> of other files for that matter.

man 5 resolver

see also: resolver(3), resolv+(8),...

Greetings
Bernd
-- __


  o--o           *QUAK* Jetzt auch mit Plueschtier in der .Sig!

 
 
 

libc 4.6.27 bug

Post by Peter Berg » Mon, 20 Feb 1995 00:52:00


 > on the subject of docs... where are the documents for files like this one?
 > I have never seen a doc/man page/ or anything on resolv.conf.  And a lot
 > of other files for that matter.

You may get the sources of bind (named that is..) and be happy. :)

bye,
    Peter


 
 
 

libc 4.6.27 bug

Post by A O V Le Bla » Fri, 24 Feb 1995 22:15:54



>on the subject of docs... where are the documents for files like this one?  
>I have never seen a doc/man page/ or anything on resolv.conf.  And a lot
>of other files for that matter.

For resolv.conf, see resolver(5).  This is not to say that there may
not be some undocumented files somewhere...

     -- Owen

 
 
 

1. Found+fixed bug libc 4.6.27 - please comment

I have not crossposted because I am not sure where
to cross post.  I found and have "fixed" a bug in libc
4.6.27 - came with slackware 4.6.27.

This bug arises when one is NOT runnin NIS (yp).  There
maybe a better fix.  Also if the developer(s) of libc
could either incorporate this fix or better I would be
happy.  The bug is probably in the later version in addition
to this one.  Here is the context diff

diff -rc libc-linux.orig/yp/yplib.c libc-linux/yp/yplib.c
*** libc-linux.orig/yp/yplib.c  Fri May 27 14:34:43 1994
--- libc-linux/yp/yplib.c       Tue Jun  6 15:48:32 1995
***************
*** 812,821 ****
  __yp_check (char **dom)
  {
    char *unused;
!  
    if ('\0' == __yp_domain[0])
      if (yp_get_default_domain (&unused))
        return 0;

    if (dom)
      *dom = __yp_domain;
--- 812,823 ----
  __yp_check (char **dom)
  {
    char *unused;
!
    if ('\0' == __yp_domain[0])
      if (yp_get_default_domain (&unused))
        return 0;
+     else if(strcmp(__yp_domain,"(none)") == 0)  /*kmb1 950603*/
+          return 0;                              /*kmb1 950603*/

    if (dom)
      *dom = __yp_domain;

***************************************************************
The actual problem arises in the next several lines of code
that includes a call to __yp_bind with an arg that is not NULL
nor a null string.  yp_bind makes a call to __nis stuff which
fails with a   clnttcp  RPC not registered and then it returns
with value that seems to make "code" work but you get this annoying
msg of   clnttcp RPC ...   This shows up in login, tars, rcp, ...

Rgds


PS if some one knows a better place to post please repost
   this "news",   thanks

2. default special uids

3. FYI: A Bug In Libc.so.4.6.27 Causing Problem in SLIP Setup

4. Broken Xserver After Recommended Patch Update for Solaris 7 x86

5. bug in libc.so.4.6.27 ?

6. Foloppy always read only after 2.5.12?

7. FYI: A Bug in libc.so.4.6.27 Causing Problem in SLIP Setup

8. Deny login under IRIX6.5

9. /lib/libc.so.4.5.26 and /lib/libc.so.4.6.27

10. ldconfig: warning: /lib/libc.so.4.6.27 is not a ZMAGIC file, skipping

11. login breaks w. libc.4.6.27

12. Problems after installation of libc.4.6.27