From owner-p4-projects@FreeBSD.ORG Thu Sep 28 18:15:58 2006 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 E6D5216A4A7; Thu, 28 Sep 2006 18:15:57 +0000 (UTC) X-Original-To: perforce@freebsd.org Delivered-To: perforce@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D6C116A415; Thu, 28 Sep 2006 18:15:57 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8264243D53; Thu, 28 Sep 2006 18:15:55 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id B033D46BF9; Thu, 28 Sep 2006 14:15:54 -0400 (EDT) Date: Thu, 28 Sep 2006 19:15:54 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Marcin Cieslak In-Reply-To: <451A7C35.8050209@SYSTEM.PL> Message-ID: <20060928191350.L76119@fledge.watson.org> References: <200609091856.k89Iu9lN090213@repoman.freebsd.org> <20060928083623.GA1297@FreeBSD.czest.pl> <451A7C35.8050209@SYSTEM.PL> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Perforce Change Reviews , Alexander Leidinger Subject: Re: PERFORCE change 105906 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: Thu, 28 Sep 2006 18:15:58 -0000 On Wed, 27 Sep 2006, Marcin Cieslak wrote: > It may happen that implementing delivery of the process ID of the other side > of the socket - feature not available AFAIK in the FreeBSD right now - will > impose on us much deeper dive into internal socket structures. The notion of "The process ID on the other side of a socket" is nonsensical. There may be zero, one, or many processes hooked up to a socket. The situations in which you can point clearly at a process or credential are the process/credential that called connect (if any), and the process/credential that sent a message. This is the distinction between LOCAL_CREDS and SCM_CREDS, FYI. Robert N M Watson Computer Laboratory University of Cambridge