dvl@
Developer
I started a portsnap at 1:50am. It's now 2:12 and it's still running. Is this within the range of normal? I think not... and I think I know why.
FYI, right after the first paste, the 'Applying patches' message appeared. Overall, I think this took about 25 minutes on a FreeBSD 9.1 box with an AMD Phenom(tm) II X4 945 Processor (3010.21-MHz K8-class CPU) and 8 GB of RAM. Load average was near 0 at the time.
Could fetching via IPv6 (which will probably fail on this network) instead of IPv4 be the cause? I ask because:
I think I either need to disable IPv6 on this server or find a way for Portsnap to use IPv4 only.
Code:
$ ps auwx | grep snap
root 38261 0.0 0.0 44424 2464 0 I+ 1:50AM 0:00.01 sudo portsnap fetch update
root 38262 0.0 0.0 14504 2148 0 I+ 1:50AM 0:00.02 /bin/sh /usr/sbin/portsnap fetch update
root 47534 0.0 0.0 9912 1544 0 I+ 1:54AM 0:00.00 xargs /usr/libexec/phttpget your-org.portsnap.freebsd.org
root 47535 0.0 0.0 14504 2148 0 I+ 1:54AM 0:00.08 /bin/sh /usr/sbin/portsnap fetch update
root 47536 0.0 0.0 10044 1712 0 I+ 1:54AM 0:00.12 /usr/libexec/phttpget your-org.portsnap.freebsd.org bp/6553a02f599faa9af19b96195053f6f92778e45c0cc35e22d762d6ee7b
dan 48236 0.0 0.0 16280 1676 1 RL+ 2:13AM 0:00.00 grep snap
$ sudo portsnap fetch update
Password:
Looking up portsnap.FreeBSD.org mirrors... 7 mirrors found.
Fetching snapshot tag from your-org.portsnap.freebsd.org... done.
Fetching snapshot metadata... done.
Updating from Sat Aug 31 20:04:21 UTC 2013 to Wed Sep 4 01:39:59 UTC 2013.
Fetching 3 metadata patches.. done.
Applying metadata patches... done.
Fetching 0 metadata files... done.
Fetching 1513 patches.....10....20....30....40....50....60....70....80....90....100....110....120....130....140....150....160....170....180....190....200....210....220....230....240....250....260....270....280....290....300....310....320....330....340....350....360....370....380....390....400....410....420....430....440....450....460....470....480....490....500....510....520....530....540....550....560....570....580....590....600....610....620....630....640....650....660....670....680....690....700...
.710....720....730....740....750....760....770....780....790....800....810....820....830....840....850....860....870....880....890....900....910....920....930....940....950....960....970....980....990....1000....1010....1020....1030....1040....1050....1060....1070....1080....1090....1100....1110....1120....1130....1140....1150....1160....1170....1180....1190....1200....1210....1220....1230....1240....1250....1260....1270....1280....1290....1300....1310....1320....1330....1340....1350....1360....1370....1380....1390....1400....1410....1420....1430....1440....1450....1460....1470....1480....1490....1500....1510. done.
Applying patches...
FYI, right after the first paste, the 'Applying patches' message appeared. Overall, I think this took about 25 minutes on a FreeBSD 9.1 box with an AMD Phenom(tm) II X4 945 Processor (3010.21-MHz K8-class CPU) and 8 GB of RAM. Load average was near 0 at the time.
Could fetching via IPv6 (which will probably fail on this network) instead of IPv4 be the cause? I ask because:
Code:
[dan@bast:~/tmp] $ time fetch http://www.freebsd.org
fetch: http://www.freebsd.org: size of remote file is not known
www.freebsd.org 27 kB 349 kBps
real 1m15.232s
user 0m0.001s
sys 0m0.004s
[dan@bast:~/tmp] $ time fetch -4 http://www.freebsd.org
fetch: http://www.freebsd.org: size of remote file is not known
www.freebsd.org 27 kB 347 kBps
real 0m0.237s
user 0m0.000s
sys 0m0.005s
I think I either need to disable IPv6 on this server or find a way for Portsnap to use IPv4 only.