Date: Mon, 15 Apr 2002 16:47:10 -0400 From: The Anarcat <anarcat@anarcat.dyndns.org> To: lewiz <purple@lewiz.info> Cc: freebsd-questions@freebsd.org Subject: FIXED! Re: mount request denied from 192.168.0.4 for /usr/ports Message-ID: <20020415204709.GF410@lenny.anarcat.dyndns.org> In-Reply-To: <1018903454.1724.14.camel@turtle.lewiz.org> References: <20020415202725.GE410@lenny.anarcat.dyndns.org> <1018903454.1724.14.camel@turtle.lewiz.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--+jhVVhN62yS6hEJ8
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon Apr 15, 2002 at 08:44:13PM +0000, lewiz wrote:
> Hi,
>=20
> I could be wrong but I think you list the root of the mount then a
> list of directories, ie:
>=20
> /usr /usr/ports -ro 192.168.0.4
> /home /home/mp3 -ro 192.168.0.4
>=20
> or something along those lines.
> Hope that's some help.
I don't think that it was it.
I figured it out, I think. On the server, there was an entry to mount
/usr/ports on the client, so maybe mountd was preventing the mount to
avoid some kind of recursive mounts.
At any rate, mountd just spontaneously decided to allow the mount
after a few kills, so everything is all right.
A.
--=20
Pemature optimization is the root of all evil
- Donald Knuth
--+jhVVhN62yS6hEJ8
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (FreeBSD)
Comment: For info see http://www.gnupg.org
iEYEARECAAYFAjy7PE0ACgkQttcWHAnWiGelBgCdHDMd8/UcJPUYCauwIku//nIZ
XugAn3h9soc0kDIbNx4FDDsmVH5XbdCA
=oNRN
-----END PGP SIGNATURE-----
--+jhVVhN62yS6hEJ8--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020415204709.GF410>
