On Sat, 07.03.15 00:20, Alban Crequy (alban.cre...@gmail.com) wrote:
> > I figure we could open a new mount namespace and mount the file system
> > socket into the chroot, but not sure I like the idea...
>
> Maybe that's the way to do it... but where would you bind mount the
> socket file? in $CH
On Thu, 05.03.15 12:16, Alban Crequy (alban.cre...@gmail.com) wrote:
> > Hmm, but what would you do for a service that has both PrivateNetwork
> > and chroot enabled?
> >
> > I am all open for shifting things around again, but I inda would
> > prefer a solution that works universally in the end...
On 9 December 2014 at 17:28, Lennart Poettering wrote:
> On Tue, 09.12.14 16:24, Krzysztof Kotlenga (k.kotle...@sims.pl) wrote:
>
>> Hi.
>>
>> Currently notify socket is unavailable in chrooted services (again)
>> unless you bind mount it there. Is there perhaps another, less
>> cumbersome way?
>>
On 9 December 2014 at 17:28, Lennart Poettering wrote:
> On Tue, 09.12.14 16:24, Krzysztof Kotlenga (k.kotle...@sims.pl) wrote:
>
>> Hi.
>>
>> Currently notify socket is unavailable in chrooted services (again)
>> unless you bind mount it there. Is there perhaps another, less
>> cumbersome way?
>>
On Wed, 10.12.14 16:33, Krzysztof Kotlenga (k.kotle...@sims.pl) wrote:
> On Tue, 2014-12-09 at 17:28 +0100, Lennart Poettering wrote:
> > On Tue, 09.12.14 16:24, Krzysztof Kotlenga (k.kotle...@sims.pl) wrote:
> >
> >> Currently notify socket is unavailable in chrooted services (again)
> >> unless
On Tue, 2014-12-09 at 17:28 +0100, Lennart Poettering wrote:
> On Tue, 09.12.14 16:24, Krzysztof Kotlenga (k.kotle...@sims.pl) wrote:
>
>> Currently notify socket is unavailable in chrooted services (again)
>> unless you bind mount it there. Is there perhaps another, less
>> cumbersome way?
>>
>>
On Tue, 09.12.14 16:24, Krzysztof Kotlenga (k.kotle...@sims.pl) wrote:
> Hi.
>
> Currently notify socket is unavailable in chrooted services (again)
> unless you bind mount it there. Is there perhaps another, less
> cumbersome way?
>
> So far notify socket was:
> 1. abstract socket
>
>commi
