Am 14.08.19 um 12:48 schrieb Michael Chapman:
> On Wed, 14 Aug 2019, Reindl Harald wrote:
may is ask you to read the thread you are responding to?
nobody is touching the private socket
>>>
>>> systemctl will mostly use /run/systemd/private when run as root
>>
>> that's not the point -
On Wed, 14 Aug 2019, Reindl Harald wrote:
> Am 14.08.19 um 12:41 schrieb Michael Chapman:
> > On Wed, 14 Aug 2019, Reindl Harald wrote:
> >> Am 14.08.19 um 12:10 schrieb Ulrich Windl:
> >> Michael Chapman schrieb am 14.08.2019 um
> >> 11:47 in
> That's all true, but the thing we
Am 14.08.19 um 12:41 schrieb Michael Chapman:
> On Wed, 14 Aug 2019, Reindl Harald wrote:
>> Am 14.08.19 um 12:10 schrieb Ulrich Windl:
>> Michael Chapman schrieb am 14.08.2019 um 11:47
>> in
That's all true, but the thing we need to check here is that systemd
correctly
On Wed, 14 Aug 2019, Reindl Harald wrote:
> Am 14.08.19 um 12:10 schrieb Ulrich Windl:
> Michael Chapman schrieb am 14.08.2019 um 11:47
> in
> >> That's all true, but the thing we need to check here is that systemd
> >> correctly handles junk on the /run/systemd/private socket. The
On Wed, 14 Aug 2019, Ulrich Windl wrote:
> >>> Michael Chapman schrieb am 14.08.2019 um 11:47 in
> Nachricht :
> > On Wed, 14 Aug 2019, Lennart Poettering wrote:
> >> Quite frankly, invoking generic UNIX programs with fds < 3 closed is a
> >> really bad idea in general. That systemctl nowadays is
Am 14.08.19 um 12:10 schrieb Ulrich Windl:
Michael Chapman schrieb am 14.08.2019 um 11:47 in
>> That's all true, but the thing we need to check here is that systemd
>> correctly handles junk on the /run/systemd/private socket. The change on
>> the systemctl side certainly tries to
>>> Michael Chapman schrieb am 14.08.2019 um 11:47 in
Nachricht :
> On Wed, 14 Aug 2019, Lennart Poettering wrote:
>> Quite frankly, invoking generic UNIX programs with fds < 3 closed is a
>> really bad idea in general. That systemctl nowadays is particularly
>> careful and deals with situations
