Re: portsdb -Uu hung
Lowell Gilbert <[EMAIL PROTECTED]> writes: > David Abrahams <[EMAIL PROTECTED]> writes: > >> I seem to be having the same problem described in >> http://www.freebsdforums.org/forums/showthread.php?t=22211, with no >> system calls shown by truss. > > My instinct is that it's unlikely to be related, even if the symptoms > look similar. > >> Unfortunately, the fix of upgrading perl from 5.6 to 5.8 doesn't apply >> to me: my version of Perl is already at 5.8.8, and probably was from >> the moment FreeBSD was installed. I'm relatively new >> at all this. Can someone help me set things right again? > > It's only happening with "-a"? > Will it upgrade individual ports okay? > Does it suck up CPU while it's hung? > Have you upgraded portupgrade to 2.2.2? It eventually finished after seeming to make no progress and not showing up in "top" for the longest time. Sorry for the false (?) alarm. -- Dave Abrahams Boost Consulting www.boost-consulting.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portsdb -Uu hung
Alex Zbyslaw wrote: 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. Just seen that portsdb -F will fetch the index and the man page even recommends running portsdb -Fu (not -Uu) after a cvsup. If -Fu still hangs for you, then you really do have a problem. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portsdb -Uu hung
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. --Alex 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. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portsdb -Uu hung
David Abrahams <[EMAIL PROTECTED]> writes: > I seem to be having the same problem described in > http://www.freebsdforums.org/forums/showthread.php?t=22211, with no > system calls shown by truss. My instinct is that it's unlikely to be related, even if the symptoms look similar. > Unfortunately, the fix of upgrading perl from 5.6 to 5.8 doesn't apply > to me: my version of Perl is already at 5.8.8, and probably was from > the moment FreeBSD was installed. I'm relatively new > at all this. Can someone help me set things right again? It's only happening with "-a"? Will it upgrade individual ports okay? Does it suck up CPU while it's hung? Have you upgraded portupgrade to 2.2.2? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
portsdb -Uu hung
I seem to be having the same problem described in http://www.freebsdforums.org/forums/showthread.php?t=22211, with no system calls shown by truss. Unfortunately, the fix of upgrading perl from 5.6 to 5.8 doesn't apply to me: my version of Perl is already at 5.8.8, and probably was from the moment FreeBSD was installed. I'm relatively new at all this. Can someone help me set things right again? TIA, -- Dave Abrahams Boost Consulting www.boost-consulting.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
