From owner-freebsd-stable Thu Jun 6 19:16:47 2002 Delivered-To: freebsd-stable@freebsd.org Received: from smtp2.knology.net (user-24-214-63-14.knology.net [24.214.63.14]) by hub.freebsd.org (Postfix) with SMTP id 2C8B037B409 for ; Thu, 6 Jun 2002 19:16:38 -0700 (PDT) Received: (qmail 10658 invoked by uid 8002); 7 Jun 2002 02:16:37 -0000 Received: from unknown (HELO grumpy.dyndns.org) (24.214.210.89) by smtp2.knology.net with SMTP; 7 Jun 2002 02:16:37 -0000 Content-Type: text/plain; charset="iso-8859-1" From: David Kelly To: Tim Kellers , Glenn Trewitt Subject: Re: smbd sucking 100% CPU Date: Thu, 6 Jun 2002 21:16:35 -0500 X-Mailer: KMail [version 1.4] Cc: References: <20020606215518.T50660-100000@serv1.wallnet.com> In-Reply-To: <20020606215518.T50660-100000@serv1.wallnet.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200206062116.35553.dkelly@HiWAAY.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thursday 06 June 2002 08:57 pm, Tim Kellers wrote: > Samba 2.2.4-1 drove me so crazy with it's refusal to authenticate > anyone to ANY share, that I pkg_deleted it (kept the MACHINE.SID), > and I've been happily, errorlessly using Samba 3.0a17 ever since. > (Ever Since about 10 days ago) Actually I haven't had any problems autheticating users. Have one user allowed to write (me) and only one share "guest" is allowed to read but not write. That was a bit of pain but SWAT is a pretty darn nice thing to have when one is shooting for a config which works. Using samba-devel is a good idea. Easier than using cvs to revert my copy of the samba port to whatever was prior. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message