** Changed in: samba (Ubuntu Intrepid)
Status: Incomplete = Won't Fix
--
Samba 3.2.3 has a memory leak that vanishes by upgrading to 3.2.5
https://bugs.launchpad.net/bugs/302969
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba
Thank you for taking the time to report this bug and helping to make
Ubuntu better. May you please try to obtain a valgrind log following the
instructions at https://wiki.ubuntu.com/Valgrind and attach the file to
the bug report. This will greatly help us in tracking down your problem.
** Changed
Marking as new so the bug doesn't auto-close. Unassigning myself since
this doesn't seem to be related to a security update.
** Changed in: samba (Ubuntu)
Assignee: Jamie Strandboge (jdstrand) = (unassigned)
Status: Incomplete = New
--
Samba 3.2.3 has a memory leak that vanishes by
Jamie,
Here is an update:
I noticed that there is a new Samba package in the repository. I
installed it per this dpkg.log entry:
2008-12-06 08:59:20 status installed samba 2:3.2.3-1ubuntu3.3
By 13:02 my system was locked up from OOM. Here is the syslog entry:
Dec 6 12:38:35 velo kernel:
Mark,
Based on your last comment, it seems that this should be marked 'Fix
Released'. Can you confirm?
--
Samba 3.2.3 has a memory leak that vanishes by upgrading to 3.2.5
https://bugs.launchpad.net/bugs/302969
You received this bug notification because you are a member of Ubuntu
Server Team,
Jamie,
There is not problem on the Ubuntu 8.10 server with Samba
3.2.3-1Ubuntu... and network mounted shares. However, that system is not
using shares accessed by Vmware 6.5.1 and Windows XP. In my opinion
there is still a problem with Samba 3.2.3-1Ubuntu... in the workstation
context where
Thank you for using Ubuntu and taking the time to report a bug. Can you
try the updated version that was fixed in
http://www.ubuntu.com/usn/USN-680-1?
** Changed in: samba (Ubuntu)
Assignee: (unassigned) = Jamie Strandboge (jdstrand)
Status: New = Incomplete
--
Samba 3.2.3 has a
Jamie,
Here is the dpkg.log entry when I installed/upgraded to that version. It
did not fix the problem (and I must say I have spent a lot of time
finding this memory leak and then the solution). It was with much
sadness of heart that I left the Ubuntu way for a tar-ball-of-old:
29291
I'm running Samba 2:3.2.3-1ubuntu3.3 on a server:
Linux frodo 2.6.27-7-server #1 SMP Thu Oct 30 05:04:11 UTC 2008 i686
GNU/Linux
and I do not have this problem.
Mark Temple wrote:
Jamie,
Here is the dpkg.log entry when I installed/upgraded to that version. It
did not fix the problem (and
