From owner-freebsd-hubs@FreeBSD.ORG Mon Mar 31 10:30:41 2008 Return-Path: Delivered-To: freebsd-hubs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AFD08106566C for ; Mon, 31 Mar 2008 10:30:41 +0000 (UTC) (envelope-from cejkar@fit.vutbr.cz) Received: from kazi.fit.vutbr.cz (kazi.fit.vutbr.cz [147.229.8.12]) by mx1.freebsd.org (Postfix) with ESMTP id 3ACA28FC19 for ; Mon, 31 Mar 2008 10:30:41 +0000 (UTC) (envelope-from cejkar@fit.vutbr.cz) Received: from kazi.fit.vutbr.cz (localhost [127.0.0.1]) by kazi.fit.vutbr.cz (envelope-from cejkar@fit.vutbr.cz) (8.14.2/8.14.1) with ESMTP id m2VADIXK075027 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 31 Mar 2008 12:13:18 +0200 (CEST) Received: (from cejkar@localhost) by kazi.fit.vutbr.cz (8.14.2/8.13.1/Submit) id m2VADI2V075026; Mon, 31 Mar 2008 12:13:18 +0200 (CEST) (envelope-from cejkar@fit.vutbr.cz) X-Authentication-Warning: kazi.fit.vutbr.cz: cejkar set sender to cejkar@fit.vutbr.cz using -f Date: Mon, 31 Mar 2008 12:13:17 +0200 From: Rudolf Cejka To: John Hay Message-ID: <20080331101317.GA70862@fit.vutbr.cz> References: <20080331094445.GA91042@zibbi.meraka.csir.co.za> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080331094445.GA91042@zibbi.meraka.csir.co.za> User-Agent: Mutt/1.5.16 (2007-06-09) X-Scanned-By: MIMEDefang 2.62 on 147.229.8.12 Cc: freebsd-hubs@freebsd.org, Garance A Drosihn Subject: Re: IPv6 and cvsup servers X-BeenThere: freebsd-hubs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD Distributions Hubs: mail sup ftp" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2008 10:30:41 -0000 John Hay wrote (2008/03/31): > I use socat on cvsup.za.freebsd.org. Something like: > /usr/local/bin/socat -ly TCP6-LISTEN:5999,fork,reuseaddr TCP4:127.0.0.1:5999 Hello, cvsup.cz.FreeBSD.org should accept IPv6 cvsup connections too. As a quick how-to for the others, you can put -- #!/bin/sh nohup /usr/local/bin/socat -ly \ tcp6-listen:5999,fork,reuseaddr \ tcp4:localhost:5999 >/dev/null 2>&1 & -- into your /etc/rc.local, or patch socat with --- socat.c.orig Tue Mar 6 22:03:28 2007 +++ socat.c Fri Mar 9 18:04:33 2007 @@ -280,7 +280,7 @@ #endif /* WITH_MSGLEVEL <= E_DEBUG */ /* not sure what signal should print a message */ - Signal(SIGHUP, socat_signal); + Signal(SIGHUP, SIG_IGN); Signal(SIGINT, socat_signal); Signal(SIGQUIT, socat_signal); Signal(SIGILL, socat_signal); @@ -1295,7 +1295,6 @@ break; case SIGTERM: Warn1("exiting on signal %d", signum); break; - case SIGHUP: case SIGINT: Notice1("exiting on signal %d", signum); break; } -- and put socat into rc.local in a simpler form: -- #!/bin/sh /usr/local/bin/socat -ly \ tcp6-listen:5999,fork,reuseaddr \ tcp4:localhost:5999 & -- The problem is that socat does not survive booting sequence, because it received HUP signal, which terminates it by default. Regards. -- Rudolf Cejka http://www.fit.vutbr.cz/~cejkar Brno University of Technology, Faculty of Information Technology Bozetechova 2, 612 66 Brno, Czech Republic