Date: Sat, 25 Sep 2010 08:39:56 +1000 From: Peter Jeremy <peterjeremy@acm.org> To: Carlos Kamtha <kamtha@ak-labs.net> Cc: freebsd-net@freebsd.org Subject: Re: Server network interface problem? Message-ID: <20100924223956.GC49476@server.vk2pj.dyndns.org> In-Reply-To: <20100922183252.GC7619@ak-labs.net> References: <20100922183252.GC7619@ak-labs.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--ctP54qlpMx3WjD+/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2010-Sep-22 14:32:52 -0400, Carlos Kamtha <kamtha@ak-labs.net> wrote: >To solve this problem, i plugged out the network cable and plugged it back= in. ... >a.) Could this be an issue with the driver on this release for em0?=20 Possibly - there have been some issues with em(4) and some chipsets. Alternatively, it could equally well have been a glitch on the associated switchport. >b.) Why was I not able to ssh to the client servers while the NFS server w= as down? Logging into a client entails filesystem accesses and if any of those filesystems are NFS mounted then those accesses will block if the NFS server is non-responding. Note that by default, sshd will search /lib, /usr/lib and /usr/local/lib (as well as subordinate compat libraries) to dlopen() nss modules - which means that a local root and /usr could still block if you have a NFS mounted /usr/local. --=20 Peter Jeremy --ctP54qlpMx3WjD+/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (FreeBSD) iEYEARECAAYFAkydKLwACgkQ/opHv/APuIdDbQCfXmBeIu7anymyZSaVjLlvqqj+ QIIAn3SsHCnr6Sel+TkXoQRTeqJ7qdYA =j/ZK -----END PGP SIGNATURE----- --ctP54qlpMx3WjD+/--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100924223956.GC49476>