From owner-p4-projects@FreeBSD.ORG Tue May 8 00:04:32 2007 Return-Path: X-Original-To: p4-projects@freebsd.org Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 7947516A40A; Tue, 8 May 2007 00:04:32 +0000 (UTC) X-Original-To: perforce@freebsd.org Delivered-To: perforce@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 44CDA16A402 for ; Tue, 8 May 2007 00:04:32 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outY.internet-mail-service.net (outY.internet-mail-service.net [216.240.47.248]) by mx1.freebsd.org (Postfix) with ESMTP id 2CD3313C484 for ; Tue, 8 May 2007 00:04:31 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.32) with ESMTP; Mon, 07 May 2007 17:04:31 -0700 Received: from julian-mac.elischer.org (nat.ironport.com [63.251.108.100]) by idiom.com (Postfix) with ESMTP id 294D7125A24; Mon, 7 May 2007 17:04:31 -0700 (PDT) Message-ID: <463FBE8E.2070604@elischer.org> Date: Mon, 07 May 2007 17:04:30 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326) MIME-Version: 1.0 To: Marko Zec References: <200705072252.l47Mq4xX044896@repoman.freebsd.org> <463FB4D3.8080402@elischer.org> <200705080135.33036.zec@icir.org> In-Reply-To: <200705080135.33036.zec@icir.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Perforce Change Reviews , Marko Zec Subject: Re: PERFORCE change 119444 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 May 2007 00:04:32 -0000 Marko Zec wrote: > On Tuesday 08 May 2007 01:22:59 Julian Elischer wrote: >> Marko Zec wrote: >>> http://perforce.freebsd.org/chv.cgi?CH=119444 >>> >>> Change 119444 by zec@zec_tpx32 on 2007/05/07 22:51:07 >>> >>> Add support for free-floating ng_hub and ng_bridge instances. >>> >>> If a hook named "anchor" is created on a ng_hub or ng_bridge >>> node instance, the node will not self-destruct even if it >>> has no hooks connected. Reminder: normal behavior is that >>> hub or bridge nodes automatically destroy themselves when >>> the last hook is disconnected. >> What is this hook attached to? >> One could just as easily send them a 'become persistant' message.. >> It would be a good candidate for a generic message. >> Data is still sent to this hook. is that what is expected? > > This hook should typically disappear right after it is created, if we > use it like this: > > tpx32# ngctl mkpeer hub anchor anchor > tpx32# ngctl l > There are 3 total nodes: > Name: ngctl69865 Type: socket ID: 0000040d Num hooks: 0 > Name: Type: hub ID: 0000040b Num hooks: 0 > Name: em0 Type: ether ID: 00000004 Num hooks: 0 > > Yes, the only purpose of this is to pin-up the node. We cannot send > a 'become persistant' message to a node that doesn't exist... Or do > you have an alternative suggestion to achieve this functionality? I > really need this badly for IMUNES... > > Cheers, > > Marko there is a hook when you create it.. you send it the message, then you can remove the hook.