From nobody@FreeBSD.ORG  Wed Jul 26 05:41:45 2000
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id D764737BA32; Wed, 26 Jul 2000 05:41:44 -0700 (PDT)
Message-Id: <20000726124144.D764737BA32@hub.freebsd.org>
Date: Wed, 26 Jul 2000 05:41:44 -0700 (PDT)
From: pisjak@dbai.tuwien.ac.at
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@FreeBSD.org
Subject: amd doesn't provide directories automatically (or only after an hour)
X-Send-Pr-Version: www-1.0

>Number:         20194
>Category:       bin
>Synopsis:       amd doesn't provide directories automatically (or only after an hour)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jul 26 05:50:00 PDT 2000
>Closed-Date:    Sun Sep 2 09:58:58 PDT 2001
>Last-Modified:  Sun Sep 02 10:00:00 PDT 2001
>Originator:     Toni Pisjak
>Release:        3.4 and 4.0
>Organization:
Technical Univ. Vienna
>Environment:
FreeBSD caph.dbai.tuwien.ac.at 4.0-RELEASE FreeBSD 4.0-RELEASE #0: Mon Mar 20 22:50:22 GMT 2000     root@monster.cdrom.com:/usr/src/sys/compile/GENERIC  i386

>Description:
AMD doesn't recognice automatically new entries in the amd maps (like for
example the SOLARIS automounter does for new entries in the automount maps), 
or only after approx. one hour. Neither "ls <dir>" nor "cd <dir>" succeed.
                                                      
In our case the NIS server is a "Solaris 2.6" machine.
                                                      
Sometimes it helps, when you submit a "kill -HUP" to the AMD process.
Killing and restarting AMD seems to help always.      
                                                      

>How-To-Repeat:
Share or export the directory "/test" on a nfs server machine.
Make a new entry in amd.<DIR1> on the NIS server, for example
    test rhost:=<nfs-server>;rfs:=/test               
and rebuild the NIS maps.                             

>Fix:
These are only workarounds, not fixes:
Wait approx. one hour and then try again.
Or supply a "kill -HUP" to the AMD process.
Or kill AMD and restart it.


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: obrien 
State-Changed-When: Sun Sep 2 09:58:58 PDT 2001 
State-Changed-Why:  
This is a general issue with Amd and is not particular to amd (am-utils) 
running on FreeBSD.  Please speak to 
http://www.cs.columbia.edu/~ezk/am-utils/index.html about the issue. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=20194 
>Unformatted:
