I can't find lsof. Did you mean ls -of ? I just got back from there. From what I could tell, this time, Samba 2.2.2 is the bad guy. I copied a directory with about 7,000 files worth maybe 100M. The server ran out of memory before the copy was done. I had to cancel it and reboot the server in order to finish.
Now I'm off to research Samba problems. Thanks Ralph Zeller ([EMAIL PROTECTED]) wrote*: > >It might be useful to run lsof to see which files are causing the problem, >or if someone is opening a bunch of really big files? > >At 05:12 PM 12/20/2001 "Bob Crandell" <[EMAIL PROTECTED]> wrote: >> I have a client with a Linux server running Samba. Something is >> filling up memory and the swap space. This is dragging down to the >> point where it's unusable. They have to reboot almost every day. >> >> My question is how do I find out what is taking up all that memory? > >
