Date: Fri, 18 Apr 2014 23:59:08 +0200 From: =?iso-8859-2?Q?Edward_Tomasz_Napiera=B3a?= <trasz@FreeBSD.org> To: lev@FreeBSD.org Cc: freebsd-net@freebsd.org Subject: Re: amd(8) doesn't work in 10 and CURRENT (does auromound(8) support NFS?) Message-ID: <F19EAE86-4822-4C22-9152-CB81A02E4C2F@FreeBSD.org> In-Reply-To: <1172266612.20140418191203@serebryakov.spb.ru> References: <1172266612.20140418191203@serebryakov.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Wiadomo=B6=E6 napisana przez Lev Serebryakov w dniu 18 kwi 2014, o godz. = 17:12: > Hello, Freebsd-net. >=20 > I'm trying to use amd(8) with default config & map for "classic" task: > access NFS shares without explicit "mount" commands (which need = "sudo"). >=20 > And it seems, that amd(8) is completely broken. It dumps core after = 1-2 > minutes of working with amd-mounted share (and NFS client complains on > timeouts after that). >=20 > Is it known problem? Does somebody use amd(8) these days? >=20 > Does new "automound(8)", which "compatible with its counterparts in = OS X, > Solaris, and Linux" support NFS? Well, it would be kind of pointless if it didn't, right? ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F19EAE86-4822-4C22-9152-CB81A02E4C2F>