>Number:         9126
>Category:       misc
>Synopsis:       Using amd requires starting NFSclients
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    misc-bug-people (Misc Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Jan  6 02:39:00 2000
>Last-Modified:
>Originator:     Bjoern Labitzke
>Organization:
Bjoern Labitzke  <hermit@cs.tu-berlin.de>
   Use PGP! (Don't you use envelopes for your letters?)
>Release:        -current 06.01.2000 <NetBSD-current source date>
>Environment:
	
System: NetBSD hermit.home.cs.tu-berlin.de 1.4P NetBSD 1.4P (LABITZKE) #30: Thu Jan 6 00:26:05 CET 2000 hermit@hermit.home.cs.tu-berlin.de:/usr/src/sys/arch/i386/compile/LABITZKE i386


>Description:
	To be able to use amd "amd=YES" has to be set in rc.conf. But this
	variable is never checked in /etc/rc (and thus amd not run), if 		"nfs_client=NO" is in /etc/rc.conf. Setting "nfs_client=YES" results 
	in starting several nfsiod processes which are not necessary for 
	amd to work.
	
>How-To-Repeat:
	Set the following in /etc/rc.conf and wonder, why amd does not start:
	nfs_client=NO
	nfs_server=NO
	amd=YES
	
>Fix:
	Either reverse the change that produced this problem or adjust the new
	solution to let amd be runnable without any NFS programs.
	
>Audit-Trail:
>Unformatted: