Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 6 Jun 2002 17:03:22 -0500
From:      David Kelly <dkelly@hiwaay.net>
To:        stable@freebsd.org
Subject:   smbd sucking 100% CPU
Message-ID:  <20020606170322.A37677@grumpy.dyndns.org>

next in thread | raw e-mail | index | archive | help
Upgraded my "personal fileserver" at work to 4.6-RC2 and rebuilt all
ports that I use. Later noticed the machine was running a bit sluggish
only to find smbd was taking all the CPU cycles it could grab.

Nothing unusual in the logs. Fact is there is practically nothing in the
logs. Not even /var/log/messages. Is a master of its own domain where
there is also an NT Server on this side of the firewall/router.

Otherwise is a fairly plain Dell PII-333 Optiplex with a few ports
including samba-2.2.4_1 and netatalk-1.5.3.1,1. Common use is to overlap
the file space served by the two so my Mac and NT machines can readily
share files.

Ethernet is the built-in xl0 port. Unusual in that today it stopped
talking on that interface. Pulled the wire, reinserted, and all was fine
once again.

"sh /usr/local/etc/rc.d/samba.sh stop" always reports one PID that it
tried to kill did not exist. Immediately run it again and two do not
exist. Use top(1) or ps(1) and find smbd is still running.

Have tried building with and without CUPS. Machine doesn't have much on
it:
% ls /var/db/pkg
autoconf213-2.13.000227_1/      pkg_tarup-1.2_3/	ruby-fnmatch-1.1b_1/
cups-base-1.1.14/               pkgdb.db		ruby-optparse-0.8.6/
gmake-3.79.1_1/                 portupgrade-20020429/	samba-2.2.4_1/
m4-1.4_1/                       ruby-1.6.7.2002.05.23/	vim-lite-6.1.48/
netatalk-1.5.3.1,1/             ruby-bdb1-0.1.7/	waveplay-2001.09.24/
%

-- 
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020606170322.A37677>