Date: Fri, 3 Feb 2006 23:10:32 -0600 From: Nikolas Britton <nikolas.britton@gmail.com> To: Xn Nooby <xnooby@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: Why does portsdb -Uu run so long? Message-ID: <ef10de9a0602032110g5ff97760tb6ead7a638c1ed86@mail.gmail.com> In-Reply-To: <bdf25fde0602010241i30ed79c9x2818c3fa35abf731@mail.gmail.com> References: <bdf25fde0602010241i30ed79c9x2818c3fa35abf731@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/1/06, Xn Nooby <xnooby@gmail.com> wrote: > Since I've gone back to the "old foolproof way" of updating my system, I'= m > doing a "portsdb -Uu" again - which has always taken forever to run on my > various machines. Is there a way to speed it up (without replacing it), = or > has anyone looked at it to see if it needs rewriting? > > I worked at a place where a monthly mainframe job ran for 24 hours, and t= he > whole plant had to shutdown while it ran (which wasnt too big a deal sinc= e > it was on Sunday). When the job started taking 36 hours to run and the > original programmer was too busy to fix it, they brought in a consultant= to > help. He re-wrote the job so it ran in 15 minutes. The original program= mer > was fired two days later. Since then, I've always been suspicous of jobs > that run for long periods of time. It just does, after you cvsup new ports cd into /usr/ports and type make fetchindex. what way is the "old foolproof way"?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ef10de9a0602032110g5ff97760tb6ead7a638c1ed86>