From owner-freebsd-questions@FreeBSD.ORG Mon Nov 2 16:09:44 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DBE69106566B for ; Mon, 2 Nov 2009 16:09:44 +0000 (UTC) (envelope-from tajudd@gmail.com) Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by mx1.freebsd.org (Postfix) with ESMTP id B13DC8FC17 for ; Mon, 2 Nov 2009 16:09:44 +0000 (UTC) Received: by pwj8 with SMTP id 8so2083624pwj.3 for ; Mon, 02 Nov 2009 08:09:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=2iRF/JciPggNkmANKEtkouop5j4OcjMxVRzqahwbKSI=; b=TpVHm2f8Gb5q8Io9rj53SNW/ME1ZqQ5ZQrsgV84O56m8X1Rk2GH9MFVYLgDU/a60j0 5qElPWv6kuiE5y1WhjG2Cg9M38PrFRWhLQ7tS7PoLFr8I1zLW86SeWwg4NYKFedipqof 3DYt98oTB97ZLyjhOogSHk6j0hCCPNUm4yaWs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=A/EGL9B/gC5OpcxEH1zfR4t86H6eVEka+1jkHnMvI+xWWuyUYirzOKtes/FuNi9qwr Ifk0sXQcZ/TmcBrQeo1fuqHVLAEuUqLAZr9sAWzno+v0fcKmtiw/AALKxEnsAbMVzAm7 XTkJ2R2lh694rYb8CntitE2mzR4U1cJbcXpXI= MIME-Version: 1.0 Received: by 10.114.7.32 with SMTP id 32mr9017699wag.107.1257178184254; Mon, 02 Nov 2009 08:09:44 -0800 (PST) In-Reply-To: <20091102133551.62B22986025@mail.farmington.k12.mo.us> References: <20091102133551.62B22986025@mail.farmington.k12.mo.us> Date: Mon, 2 Nov 2009 09:09:44 -0700 Message-ID: From: Tim Judd To: David Patton Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-questions@freebsd.org Subject: Re: issues with email migration X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2009 16:09:44 -0000 On 11/2/09, David Patton wrote: > This morning, I tried adding this to rc.conf and moved my link for /www from > local to the nfs . > > rpc_lockd_enable="YES" > rpc_statd_enable="YES" Adding them alone just tells the system at startup to start these............. > > and I experienced the same issues I had before. It would seem that postfix > and other assorted mail programs have no issue with accessing /mail on an > nfs share but everything residing in /www don't seem to like it at all. > Did you start statd and lockd by hand before trying the /www again? > I have no choice but to leave this as it is and set up a similar arrangement > on my new server. > > Thank you to everyone who responded. > > -----Original Message----- > From: Tim Judd [mailto:tajudd@gmail.com] > Sent: Saturday, October 31, 2009 10:51 AM > To: david@farmington.k12.mo.us > Cc: freebsd-questions@freebsd.org > Subject: Re: issues with email migration > > On 10/31/09, david@farmington.k12.mo.us wrote: >> only one issue with that. The server in question is an emc clereon(sorry >> not at work to look at the specifics) and at this point the only access I >> have to it is a web interface and am unable to access a command line. >> >> Also a stupid question my plan is to set up another server to access the >> nfs share to provide better email service. >> >> would this impact it in any way? > > > > > Not if file locking and the daemons take care of everything like they > should. Remember, file locking is mandatory for some things, > especially mbox files, password files, or anything else that requires > exclusive access to a file. > > If two systems try to access the same locked file, the 2nd will be > told it won't be able to get an exclusive lock, because the 1st > already has it locked. > > You're on the right track. Keep it going. > > > > > >