From owner-p4-projects@FreeBSD.ORG  Mon May  7 23:35:42 2007
Return-Path: <owner-p4-projects@FreeBSD.ORG>
X-Original-To: p4-projects@freebsd.org
Delivered-To: p4-projects@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 8ABA716A406; Mon,  7 May 2007 23:35:42 +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 27D2716A402;
	Mon,  7 May 2007 23:35:42 +0000 (UTC) (envelope-from zec@icir.org)
Received: from xaqua.tel.fer.hr (xaqua.tel.fer.hr [161.53.19.25])
	by mx1.freebsd.org (Postfix) with ESMTP id D4D6E13C45B;
	Mon,  7 May 2007 23:35:41 +0000 (UTC) (envelope-from zec@icir.org)
Received: by xaqua.tel.fer.hr (Postfix, from userid 20006)
	id E42BC9B647; Tue,  8 May 2007 01:35:40 +0200 (CEST)
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on xaqua.tel.fer.hr
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 
	autolearn=ham version=3.1.7
Received: from [192.168.200.106] (zec2.tel.fer.hr [161.53.19.79])
	by xaqua.tel.fer.hr (Postfix) with ESMTP id 1AA5C9B645;
	Tue,  8 May 2007 01:35:40 +0200 (CEST)
From: Marko Zec <zec@icir.org>
To: Julian Elischer <julian@elischer.org>
Date: Tue, 8 May 2007 01:35:32 +0200
User-Agent: KMail/1.9.6
References: <200705072252.l47Mq4xX044896@repoman.freebsd.org>
	<463FB4D3.8080402@elischer.org>
In-Reply-To: <463FB4D3.8080402@elischer.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200705080135.33036.zec@icir.org>
Cc: Perforce Change Reviews <perforce@freebsd.org>, Marko Zec <zec@freebsd.org>
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 <p4-projects.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/p4-projects>,
	<mailto:p4-projects-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/p4-projects>
List-Post: <mailto:p4-projects@freebsd.org>
List-Help: <mailto:p4-projects-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/p4-projects>,
	<mailto:p4-projects-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 07 May 2007 23:35:42 -0000

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: <unnamed>     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