Re: git svn clone terminating prematurely (I think)

From: Steven Michalske <smichalske@gmail.com>
Date: Jan 13, 2012, 07:10 UTC
Message-ID: <FDD0F00A-8BD3-466A-95A6-03FBEE0E068D@gmail.com>
In-Reply-To: <CAJ1a7SpRP5GymPrpEchuNk3xwkJLHBKjsXY_85Xs_LAzXtWYuw@mail.gmail.com>

Steven,

In this case nohup seems like a pain. There is a utility called "screen" available on most unixes. It allows you to create a virtual terminal that you can detach from. After you detach you can log out, some time later log back in and then reattach.

Steve

On Jan 12, 2012, at 10:25 AM, Steven Line wrote:

Show 23 quoted lines

> Thank you Jonathan.
> 
> I had a breakthrough yesterday on this problem.  To make a long story
> short my ssh connection to the server where I was running 'nohup git
> svn clone' was timing out.  Additionally the nohup I was using wasn't
> really protecting the git svn clone process so an hour or two after
> the ssh disconnected, the git would terminate leaving me with an
> imcomplete repository.  I don't understand why the nohup wasn't
> working yet.  So my problem wasn't due to git itself.
> 
> I started my most recent git svn clone and it's now been running for
> 18 hours.  I'm optimistic that I've solved the problem.  If my git
> does terminate early then I'll try a 'git svn fetch' to complete the
> clone, based on what you said in your post.
> 
> -- 
> Steven Line
> 303-910-1212
> sline00@gmail.com
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html