On Fri, Jan 24, 2014 at 2:02 AM, Lennart Poettering
wrote:
> On Thu, 23.01.14 11:27, David Timothy Strauss ([email protected]) wrote:
>
>>
>> Has anyone looked at using socketat() for this? It's unclear whether
>> that syscall actually exists in any supported form; it's certainly not
>> docum
On Thu, 23.01.14 11:27, David Timothy Strauss ([email protected]) wrote:
>
> Has anyone looked at using socketat() for this? It's unclear whether
> that syscall actually exists in any supported form; it's certainly not
> documented.
>
> [1] http://lwn.net/Articles/407495/
I don't think thi
2014/1/23 David Timothy Strauss :
> Has anyone looked at using socketat() for this? It's unclear whether
> that syscall actually exists in any supported form; it's certainly not
> documented.
>
> [1] http://lwn.net/Articles/407495/
grep -ir socketat linux-3.12 doesn't return anything, so unfortuna
Has anyone looked at using socketat() for this? It's unclear whether
that syscall actually exists in any supported form; it's certainly not
documented.
[1] http://lwn.net/Articles/407495/
___
systemd-devel mailing list
[email protected]
On Fri, 17.01.14 17:11, Alex Polvi ([email protected]) wrote:
> Hello,
>
> Is there a way to have a .socket bind in a particular network
> namespace? The use case is to have a container with isolated
> networking be able to start a service, or tunnel to a remote service,
> that exists outside the co
JoinsNamespaceOf= probably only works for services because of how
namespace setup gets done just before forking off a process. I think a
socket get created in the namespace of the process instantiating it.
I'm not sure there's actually a way for PID 1 systemd to set up a
socket in a namespace othe
On Sat, Jan 18, 2014 at 7:45 AM, Peeters Simon wrote:
> 2014/1/18 Alex Polvi :
>> Hello,
>>
>> Is there a way to have a .socket bind in a particular network
>> namespace? The use case is to have a container with isolated
>> networking be able to start a service, or tunnel to a remote service,
>> t
2014/1/18 Alex Polvi :
> Hello,
>
> Is there a way to have a .socket bind in a particular network
> namespace? The use case is to have a container with isolated
> networking be able to start a service, or tunnel to a remote service,
> that exists outside the containers namespace.
>
> Thank you for
Hello,
Is there a way to have a .socket bind in a particular network
namespace? The use case is to have a container with isolated
networking be able to start a service, or tunnel to a remote service,
that exists outside the containers namespace.
Thank you for any leads. I could not find anything
