Memory Leak
John Bollard
john at pbs.com
Fri Dec 8 19:40:33 GMT 2000
I have searched the archives and found a few references to
what I believe our problem is, but I would like to provide
details on our situation and see if anyone has more feedback.
Environment:
Solaris 2.6
Samba 2.0.0 (I know, upgrade. It is a client of ours that
is very reluctant to upgrade without knowing
for sure that this will help.)
Compiled with gcc 2.8.1 ( I have seen that this may be the issue)
The problem appears to be a serious memory leak. the following top
output shows just how serious.
PID USERNAME THR PRI NICE SIZE RES STATE TIME CPU COMMAND
23116 cs421 3 20 0 191M 47M cpu14 264:36 21.93% _progres
29957 sy106 3 21 0 192M 48M run 49:24 15.97% _progres
18422 root 1 31 0 690M 617M cpu14 10:16 9.27% smbd
27095 root 1 43 0 691M 456M sleep 10:24 2.60% smbd
13191 sy105 3 22 0 192M 48M sleep 1:26 2.01% _progres
5451 root 4 58 0 16M 4888K sleep 2:53 1.97% _prooidv
29137 root 1 0 0 2400K 1880K cpu15 0:17 1.27% top
28784 sy109 3 48 0 192M 48M sleep 0:22 1.27% _progres
23927 root 1 50 0 2400K 1504K sleep 8:57 1.23% top
5188 sy106 1 48 0 3248K 1728K sleep 2:33 1.21% ace_driver
1589 cs421 3 58 0 193M 49M sleep 1:31 0.75% _progres
910 mh143 3 40 0 11M 6120K sleep 0:00 0.52% _progres
15619 cs732 3 54 0 193M 49M sleep 1:29 0.39% _progres
629 ac112 3 52 0 192M 49M sleep 0:01 0.31% _progres
417 root 1 58 0 912K 608K sleep 4:27 0.25% utmpd
You can see there appears to be 2 runaway smbd processes.
The first one (18422) does not show up in smbstatus. The second (27095)
does show up.
More information about the samba
mailing list