Date: Sun, 23 Apr 2006 18:20:52 -0700 (PDT) From: Jeremy Chadwick <freebsd@jdc.parodius.com> To: FreeBSD-gnats-submit@FreeBSD.org Subject: kern/96242: rpcbind ignores NO_INET6=yes in make.conf Message-ID: <20060424012052.EC2EE5E33@mx1.parodius.com> Resent-Message-ID: <200604240130.k3O1UGA0093427@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 96242 >Category: kern >Synopsis: rpcbind ignores NO_INET6=yes in make.conf >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Apr 24 01:30:16 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Jeremy Chadwick >Release: FreeBSD 6.1-RC i386 >Organization: Parodius Networking >Environment: FreeBSD eos.parodius.com 6.1-RC FreeBSD 6.1-RC #0: Sun Apr 23 17:10:37 PDT 2006 root@eos.parodius.com:/usr/obj/usr/src/sys/EOS i386 >Description: This appears to be a repeat of the situation in PR 73865, except for 6.1. It appears 6.1 does something different... When starting rpcbind with a kernel that lacks INET6 support, even despite NO_INET6=true being in make.conf, users are shown the following: Apr 23 17:51:12 eos rpcbind: cannot get information for udp6 Apr 23 17:51:12 eos rpcbind: cannot get information for tcp6 Possibly the problem is within libc, because rpcbind relies on the libc call __rpc_nconf2sockinfo() to determine whether or not to spit out the above warning message? What I'm trying to say is using NOINET6 on FreeBSD 5.x fixes this, while using NO_INET6 on FreeBSD 6.x does not. Details of commits to rpcbind recently: http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/rpcbind/#dirlist >How-To-Repeat: `/etc/rc.d/rpcbind start` on a system which lacks INET6 support in the kernel. >Fix: None at this time. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060424012052.EC2EE5E33>