Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!news.cs.su.oz.au!inferno.mpx.com.au!news.ci.com.au!brian.telstra.net!act.news.telstra.net!vic.news.telstra.net!news.mira.net.au!news.pangea.ca!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!howland.erols.net!gatech!news-relay.ncren.net!unc-cs!not-for-mail
From: parris@cs.unc.edu (Mark Parris)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: amd: mount: Bad address
Date: 1 Jul 1997 17:13:50 -0400
Organization: The University of North Carolina at Chapel Hill
Lines: 36
Distribution: usa
Message-ID: <5pbrue$ksl@particle.cs.unc.edu>
NNTP-Posting-Host: particle.cs.unc.edu
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:44016
I've recently upgraded to 2.2.2 and since the upgrade amd has quit working
properly, giving an error like:
amd[17616]: /tmp_mnt/buzzard/dirt: mount: Bad address
Here's my uname info:
FreeBSD taz.cs.unc.edu 2.2.2-RELEASE FreeBSD 2.2.2-RELEASE #0: Tue May 20
10:45:24 GMT 1997 jkh@time.cdrom.com:/usr/src/sys/compile/GENERIC i386
My amd.map:
/defaults type:=host;fs:=${autodir}/${rhost};rhost:=${key}
* opts:=rw,grpid
And amdflags in rc.conf:
amdflags="-a /tmp_mnt -c 1800 -k i386 -d cs.unc.edu -l syslog /net
/etc/amd.map"
(wrapped for readability, all on one line in the rc.conf)
I still have one of my machines running 2.2-RELEASE FreeBSD 2.2-RELEASE #0
with the same options, map, etc. and it works fine, just as the upgraded
machine used to. I can mount the remote file-systems manually with no
problems. I tried removing /tmp_mnt in its entirety and restarting but that
didn't help either.
I would appreciate any suggestions or insight.
Thanks,
Mark Parris
parris@cs.unc.edu
--
Mark Parris - parris@cs.unc.edu