On Friday 04 November 2005 04:22, Nigel Wade wrote: > Reuben D. Budiardja wrote: > > However, when I run this program on my desktop: AMD64 FC 4 64-bit, the > > program does not terminate after a while. But it grinds this machine to > > almost to a halt, and I got page-swapping, etc. I finally managed to kill > > the program. > > That's what you would expect to happen if you are allowed to allocate the > full virtual memory space. So is this hardcoded in the kernel somehow, which differs from 64-bit to 32-bit ? > > > My question is, why does this happen in FC-4 64-bit ? what is the > > difference on this machine and other machine ? > I would expect the difference is in your user limits. On the other machines > you must have a limit set which is less than the physical memory. "ulimit -a" shows the same on the other machines I tried on. I've also looked at /etc/security/limits.conf and they are the same. So I am not sure where else it could be set. > Try ulimit -v, the virtual memory size. ulimit is a bash shell builtin. > Look at the man page for bash. Other machines may already have a limit on > virtual memory set by their admins. OK, I'll try that. Although on other machines that I try this on ulimit -v says it's unlimited (and I am the admins of those machines) and the rest are default install. Thanks. RDB
