jim wrote: > I have trouble with the idea that a swap partition is "never dropped" > once it is accessed, especially in light of the following: > > osiris# cat /proc/meminfo > total: used: free: shared: buffers: cached: > Mem: 48283648 42934272 5349376 28479488 1650688 16846848 > Swap: 94957568 0 94957568 > MemTotal: 47152 kB > MemFree: 5224 kB > MemShared: 27812 kB > Buffers: 1612 kB > Cached: 16452 kB > SwapTotal: 92732 kB > SwapFree: 92732 kB
I am having the reverse problem on my machine at work. It doesn't want to use the swap partition at all unless I force it to. I suppose that is a good thing, but what about: When I go into work I'll switch virt. consoles or type in an xterm and *poof*, there goes the X server. Then I try to run X again and it quits just as it's about to spawn the window manager. Then after I reboot, X starts up fine. This has happened every day since I've ftp-installed debian 1.3. On my previous dist I wrote a program in c that when run as root from a console will allocate all of my available memory and swap and then free it up. After doing this I was able to start X again. But I lost the code when I moved from redhat -> debian. The reason I had the code on redhat was for the same problem. But it occured infrequently. Is there something I should upgrade? I have been planning to upgrade Xfree86 to 3.3.2 but I am still a newbie with dselect, etc. I would compile it from source but the same problems happen during a compile. I had to reboot several times to get the kde and kernel sources to finish. Any help is greatly appreciated! :-) Machine: Kernel 2.0.33 X 3.3 Debian 1.3 48meg P133 -mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]