>
>
> Don't connect directly to it. Use the official bus instead. Forget
> that you know about the private connection at all...
>
> Lennart
>
>
got it, "this aren't the sockets you're looking for" :), will use then
propper `sd_bus_open_*`
Thanks Guys!
Alvaro
___
On Mo, 13.11.17 19:26, aleivag (alei...@gmail.com) wrote:
> Hi all:
>
> hope you guys are doing great!. So i have a few questions, hope this is the
> best place for them.
>
> I've been doing a lot of work with `sd-bus.h` (basically i've been trying
> to bind it to other languages to then interac
On Tue, 14 Nov 2017 at 09:19:08 +0100, Jérémy Rosen wrote:
> That being said, the system socket location is hardcoded not just in systemd,
> but in the dbus specification itself.
The D-Bus Specification does not say anything about the
.../systemd/private sockets. That would be inappropriate: those
Am 14.11.2017 um 05:26 schrieb Farhad Mohammadi Majd:
Thanks for answer Mr. Lennart, I thought GDM is always active due to
systemd, because in Wikipedia it is written in GNOME article that:
"Since GNOME 3.2 multiseat support has been only available on systems
using systemd."
so I thought it i
Op Tue, 14 Nov 2017 05:26:29 +0100 schreef Farhad Mohammadi Majd
:
Thanks for answer Mr. Lennart, I thought GDM is always active due to
systemd, because in Wikipedia it is written in GNOME article that:
"Since GNOME 3.2 multiseat support has been only available on systems
using systemd."
so
On 14/11/2017 04:26, aleivag wrote:
Hi all:
hope you guys are doing great!. So i have a few questions, hope this
is the best place for them.
I've been doing a lot of work with `sd-bus.h` (basically i've been
trying to bind it to other languages to then interact with systemd
natively).
I
