Subject: Re: [patch 1/1] /proc/$$/ipaddr and per-task networking bits
From: Arjan van de Ven <arjan@infradead.org>
To: Lorenzo =?ISO-8859-1?Q?Hern=E1ndez_?=
	 =?ISO-8859-1?Q?Garc=EDa-Hierro?= <lorenzo@gnu.org>
Cc: linux-kernel@vger.kernel.org
In-Reply-To: <1110468517.9190.24.camel@localhost.localdomain>
References: <1110464202.9190.7.camel@localhost.localdomain>
	 <1110464782.6291.95.camel@laptopd505.fenrus.org>
	 <1110468517.9190.24.camel@localhost.localdomain>
Content-Type: text/plain; charset=UTF-8
Date: Thu, 10 Mar 2005 16:38:07 +0100
Message-Id: <1110469087.6291.103.camel@laptopd505.fenrus.org>
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1035
Lines: 24

On Thu, 2005-03-10 at 16:28 +0100, Lorenzo Hernández García-Hierro
wrote:

> > 2) Can you explain briefly what this is useful for?
> 
> For keeping track on the "originating ip address of the
> task/process" (the ipv4 address of the user that started the
> task/process).

but.... tasks don't have an IP address. Hosts do. Hosts can have
multiple IP addresses. Both ipv4 and ipv6.  Users don't have IP
addresses either (they do have user IDs so that link is clear). 
I think I'm missing something big here. What does it *mean* for a task
to have an IP address. Once that is clear maybe I can start to
understand the rest, but until the meaning of "task has an IP address"
is better explained/more clear I think I'm stuck. (and no the output in
a log isn't a meaning, it's only a result)


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/