portsdb -Uu hung
xfb52 at dial.pipex.com
Wed Nov 29 07:04:58 PST 2006
Are you *sure* it's hung? -U does a "make index" in /usr/ports which
takes *forever* as it has to run a make command in *every single port*.
If you've just updated your ports tree with cvsup then consider running
"make fetchindex" from /usr/ports which just grabs the latest pre-built
version and then just doing "portsdb -u", though anything that needs the
.db file to be up-to-date will do this automatically.
PS The thread you reference seems to be about portupgrade -a which is
confusing since your subject line says portsdb -Uu. Though both part of
portupgrade, the similarity ends there.
Like Lowell said:
>Does it suck up CPU while it's hung?
What does top show for CPU usage? You will probably not see any process hogging the cpu as, like I said, it's one short make after another after another after another ... repeat until sick.
More information about the freebsd-questions