From owner-freebsd-current  Fri May  2 09:08:04 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id JAA08084
          for current-outgoing; Fri, 2 May 1997 09:08:04 -0700 (PDT)
Received: from kodiak.eos.ncsu.edu (kodiak.eos.ncsu.edu [152.1.68.61])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA08013
          for <freebsd-current@freefall.FreeBSD.org>; Fri, 2 May 1997 09:07:56 -0700 (PDT)
Received: (from camattin@localhost)
          by kodiak.eos.ncsu.edu (8.8.4/EC02Jan97)
	  id QAA18128; Fri, 2 May 1997 16:07:51 GMT
Message-Id: <199705021607.QAA18128@kodiak.eos.ncsu.edu>
Subject: Re: some quirks - inetd, setsockopt
To: kuku@gilberto.physik.rwth-aachen.de (Christoph Kukulies)
Date: Fri, 2 May 1997 12:07:51 -0400 (EDT)
Cc: freebsd-current@freefall.FreeBSD.org
In-Reply-To: <199705021537.RAA00261@gil.physik.rwth-aachen.de> from "Christoph Kukulies" at May 02, 1997 05:37:32 PM
From: camattin@ncsu.edu (Chris A. Mattingly)
Reply-To: camattin@ncsu.edu
X-Mailer: ELM [version 2.5 PL0b1/POP]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Christoph Kukulies wrote the following about "some quirks - inetd, setsockopt" on Fri May  2 11:37:32 1997
> 
> I upgraded one machine to a todays's -current with the rc.conf
> changes. 
> 
> I saw someone else already mentioning this but didn't pay attention -
> now it caught me -  What is this inetd setsockopt (SO_PRIVSTATE) about?
> 
> May  2 17:17:13 gil /kernel: changing root device to sd0a
> May  2 17:17:14 gil mountd[91]: Gethostbyname failed for mozart
> May  2 17:17:14 gil mountd[91]: Bad exports list line /a -alldirs -maproot
> May  2 17:17:14 gil mountd[91]: Gethostbyname failed for bgate
> May  2 17:17:14 gil mountd[91]: Bad exports list line /usr/ftp bgate
> May  2 17:17:16 gil inetd[124]: setsockopt (SO_PRIVSTATE): Protocol not available
> 
> 
> And why does Gethostbyname (mountd) fail for some hosts ? 

I noticed this problem when I only upgraded the kernel, before my
make world.  After the make world, it went away.  Go figure. :)

-Chris
-- 
Chris Mattingly           | My views are not necessarily those of my employers
camattin@ncsu.edu         |
NC State University/ITECS | "Good programmers write good code; great 
Systems Programmer        | programmers 'borrow' good code."  -- Mike Gancarz