On Fr, 08.03.19 11:59, Mantas Mikulėnas (graw...@gmail.com) wrote:
> > dbus policy can only reference users that are available locally at any
> > time, i.e. generally system users, not human users.
> >
> >
> Hmm, but in this case, the client seems to be completely refused access to
> the bus –
Hi Lennart & Mantas,
Thanks a lot for your quick response.
Maybe you're right, dbus-daemon resolves users mentioned in its policy
files at start-up. And then adding a new user to LDAP, dbus-daemon has
not resolved yet so it do not allow to access system bus. That may be
the reason that restart
On Fri, Mar 8, 2019 at 11:54 AM Lennart Poettering
wrote:
> On Fr, 08.03.19 16:05, Bao Nguyen (bao...@gmail.com) wrote:
>
> > Hi Lennart,
> >
> > After debugging the problem, when strace the busctl call method command
> >
> > strace -f -tt busctl call org.freedesktop.systemd1
> >
On Fr, 08.03.19 16:05, Bao Nguyen (bao...@gmail.com) wrote:
> Hi Lennart,
>
> After debugging the problem, when strace the busctl call method command
>
> strace -f -tt busctl call org.freedesktop.systemd1
> /org/freedesktop/systemd1 org.freedesktop.systemd1.Manager GetUnit s
>
Hi Lennart,
After debugging the problem, when strace the busctl call method command
strace -f -tt busctl call org.freedesktop.systemd1
/org/freedesktop/systemd1 org.freedesktop.systemd1.Manager GetUnit s
sys-devices-platform-serial8250-tty-ttyS6.device
07:54:32.027830 connect(3,
