Tree hierarchy

burraugh

Hi again,
I seem to lack some fundamental understanding about trees and services because I'm stuck with the most basic task.
1) As root I created a network tree, depending on global (which holds dhcp and dbus), and enabled wpa_supplicant in it, believing it would start and connect automatically on boot like dhcpd does, but no, I need to manually start wpa_supplicant for it to work. So who's taking care of starting dhcp on boot?
2) Very similarly, my regular user has a graphics tree with pipewire and wireplumber, set as current tree and depending on global (which has the dbus user service enabled) but the services are never started. If I then try to start pipewire manually I get scandir not running error. But I can see a session tree created for the root user with my user scandir service and my xinitrc does have a 66 tree start. So I fail again to understand how or who should be starting that session tree and my user services.
So obviously I missed, or messed something up, when following the wiki.

eric

burraugh 1) As root I created a network tree, depending on global....

Be sure to enable the tree that you want.

# 66 tree enable network

Check by looking at Enabled field with the command below

# 66 tree status -g network

And obviously be sure that services associated to the tree are also enabled.

The boot@system:runtime-branch service is responsible to start all tree marked enabled by calling 66 tree start.

burraugh But I can see a session tree created for the root user with my user scandir service and my xinitrc does have a 66 tree start

Again check if the graphics tree is marked enabled.

Can you share the output of the 66 tree status -g command as root and regular user?

burraugh

eric Can you share the output of the 66 tree status -g command as root and regular user?

This pointed me to the actual issue. Without the -g option I couldn't tell if the services were running or not, so I wrongly assumed they weren't. As it happens, they were. The problem with pipewire/wireplumber lied somewhere else (fixed and working now).

eric The boot@system:runtime-branch service is responsible to start all tree marked enabled

Thanks again. I'm trying to understand how all the pieces come together.

Being this runtime-branch a oneshot service would I be right to assume this https://git.obarun.org/Obarun/66/-/blob/master/src/66/66-oneshot.c file is the responsible for handling them?

eric

66-oneshot is responsible to launch oneshot service yes