OK, two log files are attached. In my previous email, I ran "postmaster -F" and the problem still existed.
However, I let the portmaster command run a little longer just now, and after many error messages scrolling down, it managed to download the tarball file and continued executing. You can check stdout.log. Maybe it is because the file size is largger than portmaster expected. So it kept reporting error messages when timeout. So...it's not a bug? B.R. HU Dong On Sat, Aug 11, 2012 at 4:15 PM, Michael Ranner <mich...@ranner.eu> wrote: > Sorry Mr. Barton, I am living in a different time zone ;-) > > Your requested info should on the way. > > Regards > Michael > > Am 11.08.12 10:09, schrieb Doug Barton: > > Guys, these reports are useless without the information that I > asked for: > > While 'portmaster -F' is running in one window, keep an eye on > /usr/ports/distfiles and see if the file is being downloaded, and also > keep an eye on the log file in $TMPDIR to see if it is being appended to. > > Neither I nor others who have replied to this thread can reproduce the > problem you're seeing, and that is some of the oldest code in > portmaster, so I strongly suspect that there is some problem in your > environment that is causing this. In any case, I can't debug the problem > without the information in the paragraph above. > > thanks, > > Doug > > > > -- > Mit freundlichen Grüßen > > Ing. Michael Ranner > > GSM: +43 676 4155044 > Mail: mich...@ranner.eu > WWW: http://www.azedo.at/ > >
stdout.log
Description: Binary data
tmp.log
Description: Binary data
_______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
