From owner-freebsd-current Wed Jan 8 21:39:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA06181 for current-outgoing; Wed, 8 Jan 1997 21:39:58 -0800 (PST) Received: from labs.usn.blaze.net.au (labs.usn.blaze.net.au [203.17.53.30]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA06167 for ; Wed, 8 Jan 1997 21:39:50 -0800 (PST) Received: (from davidn@localhost) by labs.usn.blaze.net.au (8.8.4/8.8.4) id QAA01181; Thu, 9 Jan 1997 16:39:02 +1100 (EST) Message-ID: Date: Thu, 9 Jan 1997 16:39:02 +1100 From: davidn@unique.usn.blaze.net.au (David Nugent) To: peter@spinner.DIALix.COM (Peter Wemm) Cc: grog@lemis.de, FreeBSD-current@freebsd.org (FreeBSD current users) Subject: Re: What's happened to nfsd and mountd? References: <199701090327.LAA10608@spinner.DIALix.COM> X-Mailer: Mutt 0.56 Mime-Version: 1.0 In-Reply-To: <199701090327.LAA10608@spinner.DIALix.COM>; from Peter Wemm on Jan 9, 1997 11:27:13 +0800 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Peter Wemm writes: > get_myaddress() returns 0 > sin_family = 2 (AF_INET = 2) > sin_len = 16 (16) > sin_port = 111 > sin_addr = 127.0.0.1 > SIOCFIGCONF used 316 bytes of a buffer 1024 long Output is the same except for the very last line which reads: SIOCFIGCONF used 976 bytes of a buffer 1024 long. > Something to try on the machines that are failing.. In lib/libc/rpc/ > get_myaddress.c, change "char buf[BUFSIZ];" to something bigger, > eg: "char buf[10240];" If you got about "992 used" for the test program > above, make the change there too. After a reboot, I get: SIOCFIGCONF used 880 bytes of a buffer 10240 long. mountd still refuses to load, with the same error. :-( Regards, David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/