From: python-updater <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] python-updater won't complete
Date: Tue, 21 Oct 2008 02:53:51 +0000 (UTC) [thread overview]
Message-ID: <loom.20081021T023309-712@post.gmane.org> (raw)
Hello,
On a 586 machine, 600 MHz, 128 meg of ram. python-updater just sits:
* Starting Python Updater from 2.4 to 2.5 :
and never completes. I tried several times, same result.
The machine only an infrequently used web server, serving up about 6
static content web pages.
Does python-updater require more ram to run? the machine is
minamalistic, it runs apache2 and not much else.
I did recently switch the profile to 2008. but is has
had 2 emerge -u world updates (along with emerge sync).
I've even run revdep-rebuild and
emerge -p --update --deep --with-bdeps=y world'
which comes back clean.
These 2 lines of top are suspicious to me:
5513 root 20 0 1648 428 348 D 0.0 0.3 0:00.10 scanelf
5514 root 20 0 0 0 0 Z 0.0 0.0 0:00.00 python-update <defunct>
bugs.gentoo.org does not reveal anything useful.
thoughts and ideas are most welcome?
James
reply other threads:[~2008-10-21 2:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20081021T023309-712@post.gmane.org \
--to=wireless@tampabay.rr.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox