From hsu@clinet.fi  Sat Nov 11 00:57:50 1995
Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id AAA08052
          for <FreeBSD-gnats-submit@freebsd.org>; Sat, 11 Nov 1995 00:57:47 -0800
Received: from katiska.clinet.fi (root@katiska.clinet.fi [194.100.0.4]) by hauki.clinet.fi (8.6.12/8.6.4) with ESMTP id KAA00974 for <FreeBSD-gnats-submit@freebsd.org>; Sat, 11 Nov 1995 10:57:27 +0200
Received: (root@localhost) by katiska.clinet.fi (8.6.12/8.6.4) id KAA00945; Sat, 11 Nov 1995 10:57:28 +0200
Message-Id: <199511110857.KAA00945@katiska.clinet.fi>
Date: Sat, 11 Nov 1995 10:57:28 +0200
From: Heikki Suonsivu <hsu@clinet.fi>
Reply-To: hsu@clinet.fi
To: FreeBSD-gnats-submit@freebsd.org
Subject: mountd error message is confusing
X-Send-Pr-Version: 3.2

>Number:         815
>Category:       bin
>Synopsis:       mountd reports unknown hosts with non-informative message
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Sat Nov 11 01:00:02 PST 1995
>Closed-Date:    Fri Sep 12 09:34:29 PDT 1997
>Last-Modified:  Fri Sep 12 09:36:34 PDT 1997
>Originator:     Heikki Suonsivu
>Release:        FreeBSD 2.1.0-950928-SNAP i386
>Organization:
Clinet, Espoo, Finland
>Environment:

	generic

>Description:

	If the export file contains a host which does not exist, noone can
	mount the disk, getting "permission denied" from mount.  The reason
	appears to be in mountd, which when reading the exports file
	calls mount(2) to put export info into kernel, and gets EPERM back.
	mountd then announces:

	Nov 11 10:43:53 katiska mountd[98]: Can't change attributes for /usr. 
	Nov 11 10:43:53 katiska mountd[98]: Bad exports list line /usr -root

	It would be very useful to know for which host the mount(2) failed.
	Knowing what went wrong would be great (EPERM does not seem too
	obvious to me, and mount(2) manual page does not mention this
	possibility?)
	
>How-To-Repeat:

	Remove a host from name service and kill -HUP mountd.

>Fix:
	
	It would seem that adding more informative error message would
	be enough to fix this problem.

	Sorry, I don't have a patch to provide right now, need to get in
	bed.

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: scrappy 
State-Changed-When: Mon Oct 21 23:44:54 PDT 1996 
State-Changed-Why:  

Dust off the cobwebs - Confirm Status 
State-Changed-From-To: feedback->open 
State-Changed-By: scrappy 
State-Changed-When: Mon Oct 21 23:45:24 PDT 1996 
State-Changed-Why:  

Problem Still Exists 

---- 

From: Heikki Suonsivu <hsu@clinet.fi> 

This is still valid report, mountd should be more informative on what 
failed, in particular with hosts' existence and being duplicate. 

State-Changed-From-To: open->closed 
State-Changed-By: jlemon 
State-Changed-When: Fri Sep 12 09:34:29 PDT 1997 
State-Changed-Why:  

Fixed in mountd.c, rev 1.24, see also: PR 1981. 
>Unformatted:
