Re: portupgrade: ruby state=swread

From: Alex Zbyslaw <xfb52@xxxxxxxxxxxxxx>
Date: Thu, 28 Sep 2006 23:30:36 +0100

Pascal Bleyler wrote:

There are only 3 ports needing an update, one of this port
is ruby.
pkg_info means i have ruby18-bdb1-0.2.2 installed
and under /usr/ports/distfiles/ruby is
ruby-1.8.5.tar.gz (i think it's the update version)

All ran fine but since 1hour top shows me the following:

----
last pid: 12998; load averages: 0.47, 0.18, 0.06 up 0+03:12:40
23:28:35
41 processes: 1 running, 40 sleeping
CPU states: 0.8% user, 0.0% nice, 0.8% system, 0.4% interrupt, 98.0%
idle
Mem: 82M Active, 4340K Inact, 24M Wired, 5268K Cache, 22M Buf, 480K Free
Swap: 231M Total, 126M Used, 105M Free, 54% Inuse, 956K In

PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND
12613 root 1 -20 0 123M 87500K swread 6:29 0.05% ruby18
----

The output of portupgrade -a is also since 1hour:
<snip>
stringio.c: c.............................
strscan.c: cc................................
Generating RI...

I use FreeBSD_6.1.RELEASE without the today published
patch for FreeBSD-SA-06:23.openssl

What can i do now? I don't want to kill the update process. Dunno
what happens then.... :/

You haven't got enough free memory and the process is swapping - swread == swap read. Give it time and it should finish. If you have other processes using significant memory which you can kill off that might help.

--Alex

_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"

References:
- portupgrade: ruby state=swread
  - From: Pascal Bleyler

Prev by Date: sctp configuration under FreeBSD 6.1
Next by Date: Re: NT loader still boot first FreeBSD slice, it could not boot second or another slice
Previous by thread: Re: portupgrade: ruby state=swread
Next by thread: Re: portupgrade: ruby state=swread
Index(es):
- Date
- Thread

Relevant Pages

Re: Some processes stay active after killing its PID
... audacious windown or unmounting wdfs unit), they still run on background, ... Even if I kill its PID, ... PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND ...
(freebsd-stable)
firefox hangs second time its run
... firefox it works -- the first time. ... I can try and kill -9 it, but it just sits there, as top says: ... PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND ...
(freebsd-stable)