Hi all, Last night portsnap1 and portsnap2 broke under the combined load of the recent ports mega-commit and a broken SSH firewalling script (mea culpa...). When I woke up this morning they both had load averages of 300+ and couldn't fork to allow me to log in. :-(
I've brought portsnap1 back online, and I'm currently waiting for portsnap2 to be rebooted (no remote power on that box); in the mean time, if you run into problems using portsnap2, try adding '-s portsnap1.freebsd.org' to force that (hopefully working) mirror to be used. -- Colin Percival Security Officer, FreeBSD | freebsd.org | The power to serve Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid _______________________________________________ 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"
