Speaking of AIX on samba... (and just joined the list myself)
(Some names and dates have been changed to protect the innocent)
Samba server name: HEATHER
Samba server is an IBM RS/6000 F50 with 1.2 GB of RAM and dual ~333 MHz
ppc processors
Samba 3.0.11
AIX 4.3.3 ML10
gcc -v
Reading specs
On Tue, Feb 22, 2005 at 10:41:48AM -0600, Jeff Schoby wrote:
Extracted, compiled, and installed form samba-latest tarball source.
We have an application running on a windows 2000 server that mapps a
drive to HEATHER. This application will periodically poll the mapped
drive for files
Ok - for a directory with 30,000 files in it you need to have the
latest svn source for Samba 3.0 (this fix isn't in 3.0.11 I'm afraid
as it was deemed too big a change at too late a stage) and to follow
the advice I gave on the list about how to set up a share to
efficiently
cope with large
Gary MacKay schrieb:
Apparently nobody has a suggestion to why smbd process all of a sudden
starts sucking CPU like crazy? Restarted samba and then restarting the
entire server does not fix it. Searching the archives shows I'm not
the only one with this problem. The archives do not show what to
Matthias Spork wrote:
Gary MacKay schrieb:
Apparently nobody has a suggestion to why smbd process all of a
sudden starts sucking CPU like crazy? Restarted samba and then
restarting the entire server does not fix it. Searching the archives
shows I'm not the only one with this problem. The
Apparently nobody has a suggestion to why smbd process all of a sudden starts
sucking CPU like crazy? Restarted samba and then restarting the entire server
does not fix it. Searching the archives shows I'm not the only one with this
problem. The archives do not show what to do about it yet.
I find this often happens if you are having nameserver trouble. That's one
of the coincidences I have noticed in the past, but there are probably
others... being out of locks or resources for example. Hope this helps at
all.
_ _ _ _ ___ _ _ _
|Y#| | | |\/| | \ |\ | | | Ryan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ryan Novosielski wrote:
| I find this often happens if you are having nameserver
| trouble. That's one of the coincidences I have noticed in
| the past, but there are probably others... being out
| of locks or resources for example. Hope this helps at
