Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 09 May 2009 14:01:47 -0500
From:      Paul Schmehl <pschmehl_lists@tx.rr.com>
To:        freebsd-questions@freebsd.org
Subject:   Problems with amd
Message-ID:  <FF4F3B6B10A9CBBA5160A9A5@Macintosh-2.local>

next in thread | raw e-mail | index | archive | help
It looks like my install of amd is screwed up.  Is there a way to rebuild 
amd from source without rebuilding world?

# uname -a
FreeBSD utd65257.utdallas.edu 7.2-STABLE FreeBSD 7.2-STABLE #12: Wed May 
6 12:12:16 CDT 2009 
root@utd65257.utdallas.edu:/usr/obj/usr/src/sys/GENERIC  i386

 amd -r
May  9 13:38:22 utd65257 amd[22655]/info:  no logfile defined; using stderr
May  9 13:38:22 utd65257 amd[22655]/info:  AM-UTILS VERSION INFORMATION:
May  9 13:38:22 utd65257 amd[22655]/info:  Copyright (c) 1997-2006 Erez 
Zadok
May  9 13:38:22 utd65257 amd[22655]/info:  Copyright (c) 1990 Jan-Simon 
Pendry
May  9 13:38:22 utd65257 amd[22655]/info:  Copyright (c) 1990 Imperial 
College of Science, Technology & Medicine
May  9 13:38:22 utd65257 amd[22655]/info:  Copyright (c) 1990 The Regents 
of the University of California.
May  9 13:38:22 utd65257 amd[22655]/info:  am-utils version 6.1.5 (build 
702100).
May  9 13:38:22 utd65257 amd[22655]/info:  Report bugs to 
https://bugzilla.am-utils.org/ or am-utils@am-utils.org.
May  9 13:38:22 utd65257 amd[22655]/info:  Configured by David O'Brien 
<obrien@FreeBSD.org> on date 4-December-2007 PST.
May  9 13:38:22 utd65257 amd[22655]/info:  Built by 
root@utd65257.utdallas.edu on date Wed May  6 11:44:19 CDT 2009.
May  9 13:38:22 utd65257 amd[22655]/info:  cpu=i386 (little-endian), 
arch=i386, karch=i386.
May  9 13:38:22 utd65257 amd[22655]/info:  full_os=freebsd7.2, 
os=freebsd7, osver=7.2, vendor=undermydesk, distro=The FreeBSD Project.
May  9 13:38:22 utd65257 amd[22655]/info:  domain=utdallas.edu, 
host=utd65257, hostd=utd65257.utdallas.edu.
May  9 13:38:22 utd65257 amd[22655]/info:  Map support for: root, passwd, 
union, nis, ndbm, file, exec, error.
May  9 13:38:22 utd65257 amd[22655]/info:  AMFS: nfs, link, nfsx, nfsl, 
host, linkx, program, union, ufs, cdfs,
May  9 13:38:22 utd65257 amd[22655]/info:        pcfs, auto, direct, 
toplvl, error, inherit.
May  9 13:38:22 utd65257 amd[22655]/info:  FS: cd9660, nfs, nfs3, nullfs, 
msdosfs, ufs, unionfs.
May  9 13:38:22 utd65257 amd[22655]/info:  Network: wire="129.110.3.0" 
(netnumber=129.110.3).
May  9 13:38:22 utd65257 amd[22655]/info:  My ip addr is 127.0.0.1

This all looks OK, but look what happens when I try to load the amd.conf 
file:

# amd -F /etc/amd.conf
AMDCONF: syntax error on line 2 (section global)

Here's the first two lines of the amd.conf file:
# cat -n /etc/amd.conf
     1	# GLOBAL OPTIONS SECTION
     2	[global]
     3	auto_dir	=/.amd_net

Line two is the syntax for the global section and is correct.  I've tried 
putting spaces around the word global.  I've tried using other types of 
brackets.  Nothing works.

And there's another thing.  The /etc/defaults/rc.conf file has a flags 
line for amd:
# grep amd_flags /etc/defaults/rc.conf
bootparamd_flags=""		# Flags to bootparamd
amd_enable="NO"			# Run amd service with $amd_flags (or NO).
amd_flags="-a /.amd_mnt -l syslog /host /etc/amd.map /net /etc/amd.map"

If I add an amd_flags section to /etc/rc.conf (which should override 
what's in /etc/defaults/rc.conf, amd will not start:

# grep amd_flags /etc/rc.conf
amd_flags="-l /var/log/amd.log"

# /etc/rc.d/amd restart
Stopping amd.
Waiting for PIDS: 22821, 22821.
NFS access cache time=60
Starting amd.

# /etc/rc.d/amd status
amd is not running.

Apparently, when amd starts with the /etc/defaults/rc.conf settings, it 
does not parse the /etc/amd.conf file, which allows it to run.  But that 
means I have to edit /etc/defaults/rc.conf if I want to make any changes 
*and* I can't have an amd.conf file.  Clearly this is not correct 
behavior.  So I'd like to rebuild amd and see if that fixes the problem, 
but I don't want to rebuild world if I can avoid it.

One last thing.  Is there any way to unmount nfs mounts without rebooting 
the box?  I've tried amq -u and umount without success.  The mounts are 
stale and have been that way for almost 24 hours now.

Paul Schmehl, If it isn't already
obvious, my opinions are my own
and not those of my employer.
******************************************
WARNING: Check the headers before replying




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FF4F3B6B10A9CBBA5160A9A5>