Thank you.
I know have a deeper understanding of the this topic :)
Regards.
Chiba
2017年11月28日(火) 23:32 Lennart Poettering :
> f1;5002;0cOn Di, 28.11.17 16:16, 千葉幹正 (chib...@klab.com) wrote:
>
> > We have a few questions about systemctl and -H option.
> >
> > It looks like systemctl is communica
f1;5002;0cOn Di, 28.11.17 16:16, 千葉幹正 (chib...@klab.com) wrote:
> We have a few questions about systemctl and -H option.
>
> It looks like systemctl is communicating with /run/systemd/private in order
> to interact with systemd.
>
> However, after you log in the connected computer via ssh, it lo
Hi, i asked similar question a few weeks ago, and you probably will get a
oficial answer soon :P, but in a nutshell would be:
/run/systemd/private is a private socket and its meant for systemd tools to
communicate with systemd even if dbus daemon is down. this is specially
true during boot and shu
We have a few questions about systemctl and -H option.
It looks like systemctl is communicating with /run/systemd/private in order
to interact with systemd.
However, after you log in the connected computer via ssh, it looks like
it's trying to control systemd by going through systemd-stdio-bridge
