Memory leak with XP Clients

[Rashkae]

Try looking in the Crontabs file of your client for updatedb and ad a
--prunepath /mountpoin/ where mountpoint is where your Samba Share is
mounted on the Linux client. Note: you cant just edit the crontab
file, see man crontab for details. Also see man updatedb for syntax of
this command.

Note 2: I used to have this problem with earlier versions of Samba. It was
fixed in one update or other, I'm not sure if the update was on client or
on server (since I updated both.). But stoping updatedb from indexing the
network share fixed the problem right enough.



On Mon, 31 Dec 2001, Steve Helder wrote:

Hello,

I am having a serious problem with clients that are connecting to our
Mandrake 8.1 server that is using the Samba 2.2.2 RPM.  After a few days of
having the computers on they will start to take up 200M of ram as reported
by top.  I don't have this problem with any of the other clients, Win2k, ME,
98 or 95.

Is there a setting I need to change on the client side?  The only way to
release the memory is to reset machine.  Logoning off does not release the
memory.

Any insights or assistance would be greatly appreciated.