Re: [systemd-devel] x bits set on /run/systemd/private, any particular reason?

2016-06-27 Thread Hoyer, Marko (ADITG/SW2)
ag, 24. Juni 2016 18:31 To: Hoyer, Marko (ADITG/SW2) Cc: systemd Mailing List Subject: Re: [systemd-devel] x bits set on /run/systemd/private, any particular reason? On Fri, Jun 24, 2016 at 2:24 PM, Hoyer, Marko (ADITG/SW2) <mho...@de.adit-jv.com<mailto:mho...@de.adit-jv.com>> wrote: Hi,

Re: [systemd-devel] x bits set on /run/systemd/private, any particular reason?

2016-06-24 Thread Lennart Poettering
On Fri, 24.06.16 11:24, Hoyer, Marko (ADITG/SW2) (mho...@de.adit-jv.com) wrote: > Hi, > > I'm not an expert on Linux access right management but I'm wondering > why systemd's private socket (/run/systemd/private) has the x bits > set. Did it happen accidently? We don't do that explicitly.

Re: [systemd-devel] x bits set on /run/systemd/private, any particular reason?

2016-06-24 Thread Mantas Mikulėnas
On Fri, Jun 24, 2016 at 2:24 PM, Hoyer, Marko (ADITG/SW2) < mho...@de.adit-jv.com> wrote: > Hi, > > > > I’m not an expert on Linux access right management but I’m wondering why > systemd’s private socket (/run/systemd/private) has the x bits set. Did it > happen accidently? > Immediately after

[systemd-devel] x bits set on /run/systemd/private, any particular reason?

2016-06-24 Thread Hoyer, Marko (ADITG/SW2)
Hi, I'm not an expert on Linux access right management but I'm wondering why systemd's private socket (/run/systemd/private) has the x bits set. Did it happen accidently? Can someone explain? Best regards Marko Hoyer Advanced Driver Information Technology GmbH Software Group II (ADITG/SW2)