Date: Thu, 12 Dec 1996 14:51:42 -0800 From: John Polstra <jdp@polstra.com> To: "Eric L. Hernes" <erich@lodgenet.com> Cc: hackers@freebsd.org, roberto@eurocontrol.fr Subject: Re: Fwd: CVSup with SSH Message-ID: <199612122251.OAA01790@austin.polstra.com> In-Reply-To: Your message of "Thu, 12 Dec 1996 16:34:26 CST." <199612122234.QAA02971@jake.lodgenet.com> References: <199612122234.QAA02971@jake.lodgenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Yeay! I just tried the cvs tree, and it looks ok.
>
> >This should be _really_ useful to those poor souls who haven't been
> >able to get the SOCKS stuff working. I'm going to document it in the
> ;-) That's me!
All _right_! You've been one of my toughest cases. ;-) I'm glad there's
finally a solution for you.
> I whipped up a new fbsd-update script. I had to use expect, unless
> someone can help me out a bit with ssh from a script:
> ------------------cut--here-----------------------
> #!/usr/local/bin/expect
>
> set lport 6666
One caution: Don't everybody start using 6666, or this thing will never
work. It has to be a port that's free on both your local machine and on
the server host. If everybody starts using 6666, they'll be colliding
before long. Pick some creative individual number. Better yet, make
the script choose one semi-randomly.
> Is there anyway to get this to work without actually logging in?
I was wondering the same thing. Could some ssh expert answer that,
please?
The only idea I could think of was something like this:
ssh -L 5999:localhost:5999 -R $lport:localhost:$lport freefall sleep 3600
and then kill the ssh process with a signal when the update completes.
I haven't tried it, though.
John
--
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Self-knowledge is always bad news." -- John Barth
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199612122251.OAA01790>