to setup some systemd user services.
As root I did
Code: Select all
loginctl enable-linger ki-kmu
I get this:
[coode]
ki-kmu@rp-f083dc:~$ systemctl --user status
Failed to connect to bus: No such file or directory
ki-kmu@rp-f083dc:~$ ls /run/user/1002/ -alh
total 0
drwx------ 2 ki-kmu users 40 Jul 8 18:53 .
drwxr-xr-x 3 root root 60 Jul 8 18:53 ..
[/code]
so the dbus socket is not present. However the system wide dbus.socket is
enabled and active and dbus.service is also enabled an active.
Code: Select all
root@rp-f083dc:~# ps aux | grep dbus-daemon
message+ 1576 0.0 0.5 4896 2652 ? Ss Jul03 0:01 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
[code]
But systemd failed to launch dbus-daemon for the user ki-kmu. There is however one running
for the user messagebus, so this user sessions seems to be working.
I have no experience with red pitaya, this is the first time I have to work with
one. My client asked to help configure the auto start services. When I log in
via SSH I get on the console
[code]
##############################################################################
# Red Pitaya GNU/Linux Ecosystem
# Version: 0.99
# Build: 48
# Branch:
# Commit: 6c39f01af171044bcdb5712a0b8a62f3d5072613
# U-Boot: "redpitaya-v2016.4"
# Linux Kernel: "branch-redpitaya-v2017.2"
# Pro Applications: ""
##############################################################################
What can I do to spwan the dbus daemon for the user ki-kmu? Should the user be
in a special group?
Thanks