From owner-freebsd-current Thu Mar 9 13:42:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from everest.overx.com (everest.overx.com [63.82.145.202]) by hub.freebsd.org (Postfix) with ESMTP id 89CCA37B837 for ; Thu, 9 Mar 2000 13:42:34 -0800 (PST) (envelope-from dayton@overx.com) Received: from polo.overx.com (polo.overx.com [63.82.145.204]) by everest.overx.com (Postfix) with ESMTP id 83588203C for ; Thu, 9 Mar 2000 15:42:29 -0600 (CST) Received: by polo.overx.com (Postfix, from userid 1001) id CAE773F29; Thu, 9 Mar 2000 15:42:36 -0600 (CST) From: Soren Dayton Reply-To: dayton+freebsd-stable@overx.com To: freebsd-current@freebsd.org Subject: samba 2.0.6 crashing -stable Date: 09 Mar 2000 15:42:36 -0600 Message-ID: <86bt4n6cs3.fsf@polo.overx.com> Lines: 19 User-Agent: Gnus/5.070099 (Pterodactyl Gnus v0.99) XEmacs/21.1 (Bryce Canyon) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've been having a recurring problem with samba on my freebsd machines. It began when I was running 3.2, and it appears to still be around with -stable. (and samba 2.0.3, and now 2.0.6) Basically, when copying large files, the FreeBSD file server appears to lose all of its network connectivity. It cannot be pinged, etc. You also cannot log in as root because it hangs after you type in `root' on console. (which might be concistent with all networking failing. I think, but have not verified this, that anything that does not use NIS or some such thing will continue to work. Has anyone heard of such problems? Any ideas? Thanks. Soren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message