I have -CURRENT as of 03/14 running on a dell latitude d600. This was un upgrade from 5.3-STABLE. The laptop has 512Mb RAM and 1Gb of swap space. root_at_yoda <~> 569# df -h Filesystem Size Used Avail Capacity Mounted on /dev/ad0s1a 124M 60M 54M 53% / devfs 1.0K 1.0K 0B 100% /dev /dev/ad0s1e 16G 8.5G 6.2G 58% /usr /dev/ad0s1d 989M 62M 848M 7% /var root_at_yoda <~> 569# swapinfo Device 1K-blocks Used Avail Capacity /dev/ad0s1b 1048576 10395282 1022756 99% Today I'm trying to upgrade all glib/gtk/gnome libs following as per 20050312 (/usr/ports/UPDATING). Reasonably early during the 4th and final stage of the gnome_upgrade.sh script (GNOME_UPGRADE_SH_VER=2.10-3 (during an openoffice-1.1 build)) /var/log/messages gets flooded with the following messages: Mar 16 12:47:39 yoda kernel: pid 96533 (sort), uid 0, was killed: out of swap space Mar 16 12:47:40 yoda kernel: swap_pager: out of swap space Mar 16 12:47:40 yoda kernel: swap_pager_getswapspace(16): failed Mar 16 12:47:40 yoda kernel: pid 96611 (sort), uid 0, was killed: out of swap space Mar 16 12:47:41 yoda kernel: swap_pager: out of swap space Mar 16 12:47:41 yoda kernel: swap_pager_getswapspace(16): failed It always is referring to the sort(1) process. I've not seen this behavior before during the 2 days running -CURRENT and having upgraded several ports thru portupgrade(1). Hopefully someone can point me in the right direction. Marco -- WINDOWS: "Where do you want to go today?" LINUX: "Where do you want to go tomorrow?" BSD: "Are you guys coming or what?"
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:30 UTC