Date: Wed, 23 Jul 2008 21:33:00 -0400 From: darko <darko.listsniffer@gmail.com> To: "Tuc at T-B-O-H.NET" <ml@t-b-o-h.net> Cc: Roland Smith <rsmith@xs4all.nl>, Derek Belrose <derekb@realgeeky.com>, freebsd-questions@freebsd.org Subject: Re: [freebsd-questions] Re: Port Management on a larger scale Message-ID: <82f3feb90807231833k3efedd54l28b952763d0e21cf@mail.gmail.com> In-Reply-To: <200807232206.m6NM6vOT085271@himinbjorg.tucs-beachin-obx-house.com> References: <20080723215917.GA64673@slackbox.xs4all.nl> <200807232206.m6NM6vOT085271@himinbjorg.tucs-beachin-obx-house.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jul 23, 2008 at 6:06 PM, Tuc at T-B-O-H.NET <ml@t-b-o-h.net> wrote: > 2) Taking down or a failure of the NFS server pulls EVERY > other system with it. ..just thinking out loud here...but.. what if you had 2 identical NFS/rsync servers and used them together in a standby/failover method. i.e. when you have to bring down one NFS/rsync server, you direct all clients to the other and vice versa. > > 3) Working with lockd/statd can be problematic at times. > 4) NFS on FreeBSD varies (I'M TOLD) between versions as to > effectiveness, issues, etc. > 5) I've run into issues where some programs are just NOT > happy running over NFS (hylafax for me for example. POTENTIALLY a locking > issue, but running a locking tester shows everything fine, but it > just for the life of it won't work over NFS for me atleast). > > Since this is a "personal" system, I put up with it. When > I get the time/energy I'm going to break all the systems apart. > > Tuc/TBOH > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" > -- regards, dg "..but the more you use clever tricks, the less support you'll get ..." -- M.W.Lucas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?82f3feb90807231833k3efedd54l28b952763d0e21cf>