Hardware is x86 32-bit - Atom. Thank you for the suggestions. The issue persists even when I try other mirrors (tried 3-4 different ones). Leaving out -q shows that there is some activity. But after a while (60 mins +) it stops with the message:
"packet_write_wait: Connection to 129.128.197.20 port 22: Broken pipe" This has happened about three times now I have had ssh connections open to work over a few hours. But that is through VPN. It may be a router issue. How can I check? Will try -stable checkout instead of updating to see if hat works Thanks Hrishi On Sat, Mar 18, 2017 at 8:29 AM, Nick Holland <n...@holland-consulting.net> wrote: > On 03/17/17 12:09, Hrishikesh Muruk wrote: > > Following instructions at https://www.openbsd.org/anoncvs.html > > > > I downloaded sys.tar.gz and src.tar.gz for OpenBSD 6.0 and followed that > > with an attempt to update the source to stable. > > > > $ cvs -d anon...@anoncvs3.usa.openbsd.org:/cvs -q up -rOPENBSD_6_0 -Pd > > > > After running for a while cvs is just stuck at > > > > ? gnu/usr.bin/perl/cpan/ExtUtils-CBuilder/lib/ExtUtils/CBuilder/Platform > > ? gnu/usr.bin/perl/ext/Attribute-Handlers > > > > Seems to make no progress. The top command shows cvs WAIT state as > biowait > > and has stayed that way for more than 30 mins. > > > > Is cvs stuck or does it normally take this long for an update to stable? > > depends on your hw -- 486 or sparc, probably still busy. modern > computer (younger than 15 years old), probably stuck. > > I'd start with trying a different mirror. If that does it, you might > want to let your mirror's maintainer know you had a problem in case it > was something broke on their end. > > It might also be a problem with your connection -- a CVS update can be a > very long, sustained SSH connection, and in the case of a -stable > upgrade, perhaps a lot of time spent moving nothing, so maybe your > (non-OpenBSD) firewall timed out? I've seen commercial FWs timeout on > ssh connections before, never during a CVS update, but then, I don't do > -stable. :) (in multiple meanings!) > > You might want to try just doing a -stable checkout instead of updating > the .tgz files, since for MOST people, Internet bandwidth is not > something needing conservation. > > Nick.
