From owner-freebsd-current  Tue Jan 23 12:52:52 2001
Delivered-To: freebsd-current@freebsd.org
Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20])
	by hub.freebsd.org (Postfix) with ESMTP
	id DC25637B69C; Tue, 23 Jan 2001 12:52:31 -0800 (PST)
Received: (from bright@localhost)
	by fw.wintelcom.net (8.10.0/8.10.0) id f0NKqVw09628;
	Tue, 23 Jan 2001 12:52:31 -0800 (PST)
Date: Tue, 23 Jan 2001 12:52:31 -0800
From: Alfred Perlstein <bright@wintelcom.net>
To: John Baldwin <jhb@FreeBSD.ORG>
Cc: Julian Elischer <julian@elischer.org>, current@FreeBSD.ORG,
	green@FreeBSD.ORG
Subject: Re: mountd changed?
Message-ID: <20010123125231.D26076@fw.wintelcom.net>
References: <3A6DA32E.D92AB30C@elischer.org> <XFMail.010123124024.jhb@FreeBSD.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <XFMail.010123124024.jhb@FreeBSD.org>; from jhb@FreeBSD.ORG on Tue, Jan 23, 2001 at 12:40:24PM -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

* John Baldwin <jhb@FreeBSD.ORG> [010123 12:41] wrote:
> 
> On 23-Jan-01 Julian Elischer wrote:
> > Suddenly the following error messages occur:
> > Jan 23 07:21:02 jules mountd[435]: can't export /unused
> > Jan 23 07:21:02 jules mountd[435]: bad exports list line /unused 
> > -maproot
> > Jan 23 07:21:02 jules mountd[435]: could not remount /usr: Bad
> > address
> > Jan 23 07:21:02 jules mountd[435]: bad exports list line /usr  
> > -alldirs
> > -maproot
> > 
> > The file is:
> > /unused                 -maproot=root vjules
> > /usr    -alldirs        -maproot=root vjules
> > 
> > vjules is just fine as an address:
> > julian@jules:ping vjules
> > PING vjules (192.168.254.2): 56 data bytes
> > .....
> > 
> > CVS shows no changes to mountd recently.
> > 
> > this /etc/exports file was working fine a couple of weeks ago.
> > Is this related to the 'ucred' thing people have been talking about?
> 
> Possibly, are your kernel and world out of sync?  You should've gotten
> evil console messages about trying to malloc some obscene amount of
> memory like 128MB though.

No, he would have panic'd before seeing that.  Something else is
broken I think.

-- 
-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org]
"I have the heart of a child; I keep it in a jar on my desk."


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message