From owner-freebsd-hackers Thu Jun 17 0:37:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (Postfix) with ESMTP id 8722F15169 for ; Thu, 17 Jun 1999 00:37:07 -0700 (PDT) (envelope-from ust@cert.siemens.de) X-Envelope-Sender-Is: ust@cert.siemens.de (at relayer david.siemens.de) Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.14]) by david.siemens.de (8.9.3/8.9.3) with ESMTP id JAA14262; Thu, 17 Jun 1999 09:37:06 +0200 (MET DST) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail2.siemens.de (8.9.3/8.9.3) with ESMTP id JAA23688; Thu, 17 Jun 1999 09:37:05 +0200 (MET DST) Received: from alaska.cert.siemens.de (alaska.cert.siemens.de [139.23.202.134]) by mars.cert.siemens.de (8.9.3/8.9.3/Siemens CERT [ $Revision: 1.9 ]) with ESMTP id JAA02675; Thu, 17 Jun 1999 09:38:10 +0200 (CEST) Received: (from ust@localhost) by alaska.cert.siemens.de (8.9.3/8.9.3/alaska [ $Revision: 1.2 ]) id HAA03656; Thu, 17 Jun 1999 07:38:10 GMT (envelope-from ust) Date: Thu, 17 Jun 1999 09:38:10 +0200 From: Udo Schweigert To: John Polstra Cc: hackers@FreeBSD.ORG Subject: Re: m3socks and cvsup Message-ID: <19990617092316.B3119@alaska.cert.siemens.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i X-Mailer: Mutt 0.95.5i In-Reply-To: <199906170110.SAA66976@vashon.polstra.com>; from John Polstra on Wed, Jun 16, 1999 at 06:10:42PM -0700 X-Operating-System: FreeBSD 3.2-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jun 16, 1999 at 06:10:42PM -0700, John Polstra wrote: > Udo Schweigert wrote: > > > I'm using it (runsocks cvsup -P m) for a year now and it works > > without any problems. (Since cvsup 16 the "-P m" is not needed, so > > "runsocks cvsup" should so it). > > Just to make sure I understand: You're using standard socks rather > than m3socks, right? > > I believe that standard socks should work with cvsup's multiplexed > mode, but I've never tried it. It would probably be necessary to add > "@M3novm" to the command line, though. If standard socks works, then > I want to eliminate m3socks. There are some problems with m3socks > that I just found out about recently. > Hello John, I'm not using m3socks, I use the standard socks5 from ports (current version is socks5-1.0.8). To use it (the runsocks program) with cvsup one has to build cvsup with dynamic linking (by building port net/cvsup), the precompiled package from CD-ROM and the one from net/cvsup-bin port will not work. For example I changed in /usr/local/etc/cvsup/update.sh (contained in net/cvsup-mirror port): < cvsup -1gL 1 -c ${colldir} -h ${host} supfile --- > runsocks cvsup -P m -1gL 1 -c ${colldir} -h ${host} supfile As stated before, this works since approx. one year without any problems. As I remember, I used m3socks for a short time, but when I noticed that runsocks also worked, I changed to that. Regards ------------------------------------------------------------------------------- Udo Schweigert || Voice : +49 89 636 42170 Siemens AG, Siemens CERT || Fax : +49 89 636 48000 ZT IK 3 || email : Udo.Schweigert@mchp.siemens.de D-81730 Muenchen / Germany || : ust@cert.siemens.de PGP fingerprint || 2A 53 F6 A6 30 59 64 02 6B C4 E0 73 B2 C9 6C E7 ------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message