> Howdy all,
>
> An easy one this time I hope...
>
> I am installing a few packages on three new machines but one
> keeps saying ...
>
> swap space below 10 percent free
>
> Which causes setld to become upset. monitor reports 40%
> free swap but I am not entirely clear as to why any swap
> should be reserved anyway when the machines are doing nothing
> other than running a desktop. These machines all have 128M
> ram and 198M swap, surely that is enough for any setld. So..
>
> What is reserving the swap??
> Why does setld think that there is less free swap than monitor??
> Why does the reserved and free reported by monitor not total 100%?
>
>
Thanks to all who responded.
The general idea is...
When the system was built the vendors did not allocate sufficient
swap in the first place. This I agree with but hey if you can't get
along with 128M real and 198M virtual there is something wrong!
The non lazy swap has become confused and allocated all resource.
Use lazy swap, although this requires a reboot to switch.
My own feeling is that if you are putting a desktop together
you should provide more like three or four times real for the
virtual memory. /tmp should be mounted onto swap. Use lazy,
it's more reliable.
k.mcmanus_at_gre.ac.uk -
http://www.gre.ac.uk/~k.mcmanus
-------------------------------------------------------------
Dr Kevin McManus ||
School of Computing & Math Science ||
The University of Greenwich ||
Wellington St. Woolwich ||Tel +44 (0)181 331 8719
London SE18 6PF UK ||Fax +44 (0)181 331 8665
Received on Tue Jul 29 1997 - 18:03:27 NZST