Problems with portsdb -Uu on FreeBSD 6.3

[perikillo]

On Tue, Sep 9, 2008 at 6:13 AM, RW <fbsd06 at mlists.homeunix.com> wrote:

> On Mon, 8 Sep 2008 17:57:16 -0700
> perikillo <perikillo at gmail.com> wrote:
> > On Mon, Sep 8, 2008 at 5:26 PM, Michael Powell
> > <nightrecon at verizon.net>wrote:
> >
> Please don't top-post.
> > >
> > > Unless you have a specific overriding reason to do -Uu you might
> > > want to try -uF instead. It's what I use and it's always worked. In
> > > fact, this is what I do to see if I need an upgrade:
> > >
> > > csup -L 2 ports && portsdb -uF && pkgdb -u && portversion
> > >
> > > But since I have never used portsnap don't really know anything
> > > about it.
> > >
> > > -Mike
> >    I have been trying a lot of things, I want to start again, I think
> > I just need to delete /usr/ports?
> >
> >    Let me read again the manual and see those Flags.
> >
> >    I remember that the first time u run portsdb the manuals recommend
> > to sue Uu, but let read the manual page, I will back soon!!!
>
>
> portsdb -F and portsdb -U, both update the index file. The first
> downloads it, the second creates it from scratch (which is slow).
> Portsnap handles this automatically, so neither will be needed.
>
> The work done by portsdb -u will be done automatically when portupgrade
> is next run, but it may save a little time later.
>
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> freebsd-questions-unsubscribe at freebsd.org"
>

   After finally realize that running portsdb -Uu each time I sync my ports
is not a good way, I will follow the Michael Powell tip. Thanks all for your
help, I still don't know why always appear the port apcupsd went this thing
crush.

   Thanks all for your great help!!!