> -Original Message-
> From: Petr Machata [mailto:pe...@mellanox.com]
> Sent: Monday, September 16, 2019 2:56 AM
> To: Keller, Jacob E
> Cc: Jiri Benc ; linuxptp-devel@lists.sourceforge.net
> Subject: Re: [Linuxptp-devel] [PATCH 2/2] pmc: Support querying
> TLV_PORT_PROPERTIES_NP
>
>
>
Jiri Benc writes:
> On Mon, 16 Sep 2019 09:56:29 +, Petr Machata wrote:
>> Inside the namespace you can do "ip netns id" to get the namespace that
>> you are in.
>
> Beware that this netnsid is only valid in the net name space that the
> 'ip' command ran in. It is not a global identifier
Jiri Benc writes:
> On Mon, 16 Sep 2019 14:04:00 +, Petr Machata wrote:
>> I was actually thinking about /var/run/netns being mounted elsewhere or
>> some such, which would prevent "ip netns id" from working. The symbolic
>> names seem to be accessible from other namespaces just fine --"ip
On Mon, 16 Sep 2019 14:04:00 +, Petr Machata wrote:
> I was actually thinking about /var/run/netns being mounted elsewhere or
> some such, which would prevent "ip netns id" from working. The symbolic
> names seem to be accessible from other namespaces just fine --"ip netns
> exec foo ip netns
On Mon, 16 Sep 2019 09:56:29 +, Petr Machata wrote:
> Inside the namespace you can do "ip netns id" to get the namespace that
> you are in.
Beware that this netnsid is only valid in the net name space that the
'ip' command ran in. It is not a global identifier and it is not valid
in another
Keller, Jacob E writes:
>> From: Petr Machata [mailto:pe...@mellanox.com]
>> Sent: Friday, September 13, 2019 7:58 AM
>> To: Jiri Benc
>> Cc: linuxptp-devel@lists.sourceforge.net
>> Subject: Re: [Linuxptp-devel] [PATCH 2/2] pmc: Support querying
>> TLV_PORT_PROPERTIES_NP
>>
>> Jiri Benc
