one question, are you certain that your user-id (z) is 1002?

you probably need to re-enable boot-user properly

e.g.: # 66-enable -zv3 -t boot-user -F boot-user@ z
z@ obarunS6 ~ % 66-inservice -o logfile -p 50 pulseaudio
Log file              : 
2021-02-20 17:01:35.703482444  W: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /run/user/1002/bus: No such file or directory
2021-02-20 17:01:35.703505497  W: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /run/user/1002/bus: No such file or directory
2021-02-20 17:01:55.606537503  E: [pulseaudio] main.c: Failed to kill daemon: No such process
2021-02-20 17:01:55.836034891  W: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /run/user/1002/bus: No such file or directory
2021-02-20 17:01:55.836041016  W: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /run/user/1002/bus: No such file or directory
2021-02-20 17:02:06.930369866  E: [pulseaudio] main.c: Failed to kill daemon: No such process
2021-02-20 17:02:07.156677760  W: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /run/user/1002/bus: No such file or directory
2021-02-20 17:02:07.156707234  W: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /run/user/1002/bus: No such file or directory
2021-02-20 17:02:27.077579071  E: [pulseaudio] main.c: Failed to kill daemon: No such process
2021-02-20 17:02:27.336339925  W: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /run/user/1002/bus: No such file or directory
2021-02-20 17:02:27.336345881  W: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /run/user/1002/bus: No such file or directory
2021-02-20 17:02:47.223114793  E: [pulseaudio] main.c: Failed to kill daemon: No such process
2021-02-20 17:02:47.485365813  W: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /run/user/1002/bus: No such file or directory
2021-02-20 17:02:47.485388819  W: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /run/user/1002/bus: No such file or directory
2021-02-20 17:03:07.389211710  E: [pulseaudio] main.c: Failed to kill daemon: No such process
2021-02-20 17:03:07.626089550  W: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /run/user/1002/bus: No such file or directory
2021-02-20 17:03:07.626111586  W: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /run/user/1002/bus: No such file or directory
2021-02-20 17:03:27.543031209  E: [pulseaudio] main.c: Failed to kill daemon: No such process
2021-02-20 17:03:27.769912787  W: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /run/user/1002/bus: No such file or directory
2021-02-20 17:03:27.769935550  W: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /run/user/1002/bus: No such file or directory
2021-02-20 17:03:47.689532089  E: [pulseaudio] main.c: Failed to kill daemon: No such process
2021-02-20 17:03:47.910820540  W: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /run/user/1002/bus: No such file or directory
2021-02-20 17:03:47.910849302  W: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /run/user/1002/bus: No such file or directory
2021-02-20 17:04:07.830579392  E: [pulseaudio] main.c: Failed to kill daemon: No such process
2021-02-20 17:04:08.091086247  W: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /run/user/1002/bus: No such file or directory
2021-02-20 17:04:08.091092205  W: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /run/user/1002/bus: No such file or directory
2021-02-20 17:04:27.984201981  E: [pulseaudio] main.c: Failed to kill daemon: No such process
2021-02-20 17:04:28.211865259  W: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /run/user/1002/bus: No such file or directory
2021-02-20 17:04:28.211871379  W: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /run/user/1002/bus: No such file or directory
2021-02-20 17:04:48.111165432  E: [pulseaudio] main.c: Failed to kill daemon: No such process
2021-02-20 17:04:48.366485057  W: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /run/user/1002/bus: No such file or directory
2021-02-20 17:04:48.366515732  W: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /run/user/1002/bus: No such file or directory
2021-02-20 17:05:08.272386014  E: [pulseaudio] main.c: Failed to kill daemon: No such process
2021-02-20 17:05:08.547841203  W: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /run/user/1002/bus: No such file or directory
2021-02-20 17:05:08.547879352  W: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /run/user/1002/bus: No such file or directory
2021-02-20 17:05:28.432291684  E: [pulseaudio] main.c: Failed to kill daemon: No such process
2021-02-20 17:05:48.576556754  E: [pulseaudio] main.c: Failed to kill daemon: No such process
2021-02-20 18:33:54.814446676  W: [alsa-sink-Audio 8 DJ] alsa-util.c: Got POLLNVAL from ALSA
2021-02-20 18:33:54.814485128  W: [alsa-source-Audio 8 DJ] alsa-util.c: Got POLLNVAL from ALSA
2021-02-20 18:33:54.814657188  W: [alsa-source-Audio 8 DJ] alsa-util.c: Got POLLNVAL from ALSA
2021-02-20 18:33:54.814702010  W: [alsa-source-Audio 8 DJ] alsa-util.c: Got POLLNVAL from ALSA
2021-02-20 18:33:54.814734573  W: [alsa-sink-Audio 8 DJ] alsa-util.c: Got POLLNVAL from ALSA
2021-02-20 18:33:54.814766106  W: [alsa-sink-Audio 8 DJ] alsa-util.c: Got POLLNVAL from ALSA
2021-02-20 18:33:54.814923268  W: [alsa-source-Audio 8 DJ] alsa-util.c: Got POLLNVAL from ALSA
2021-02-20 18:33:54.814940763  W: [alsa-sink-Audio 8 DJ] alsa-util.c: Got POLLNVAL from ALSA
2021-02-20 18:33:54.916387105  E: [alsa-sink-Audio 8 DJ] alsa-sink.c: Error opening PCM device hw:1,0,0: No such file or directory
2021-02-20 18:33:54.916414227  E: [alsa-source-Audio 8 DJ] alsa-source.c: Error opening PCM device hw:1,0,2: No such file or directory
2021-02-20 22:31:54.762599037  E: [pulseaudio] main.c: Failed to kill daemon: No such process
2021-02-20 22:33:46.772831301  E: [pulseaudio] main.c: Failed to kill daemon: No such process
@ negative. This is not the trouble here, the last output of his trees show a running boot-user@ z service(and all its service inside).

Your log output confuse me a lot! I don't see any reason to have issue now.

Please to be sure of what happens follow this instructions: 
% 66-stop -u pulseaudio
% 66-disable -R pulseaudio # this command will remove everything of the service(log,conf,etc)
% 66-enable pulseaudio
% 66-start pulseaudio
then resend the output of 
% 66-inservice pulseaudio
4 days later
hm, now everything seems fine. i'll tell you what happens next time i boot
and remove the manual 'export'
z@ obarunS6 ~ % 66-stop -u pulseaudio
66-stop: info: Stopped successfully: pulseaudio
66-stop: info: Stopped successfully: pulseaudio-log
66-stop: info: Unsupervised successfully: pulseaudio
66-stop: info: Unsupervised successfully: pulseaudio-log
z@ obarunS6 ~ % 66-disable -R pulseaudio 
66-disable: info: Disabled successfully: pulseaudio
66-disable: info: Disabled successfully: pulseaudio-log
z@ obarunS6 ~ % 66-enable pulseaudio
66-enable: info: Enabled successfully: pulseaudio
z@ obarunS6 ~ % 66-start pulseaudio
66-start: info: Initialized successfully: pulseaudio-log
66-start: info: Initialized successfully: pulseaudio
66-start: info: Started successfully: pulseaudio-log
66-start: info: Started successfully: pulseaudio
z@ obarunS6 ~ % 66-inservice pulseaudio
Name                  : pulseaudio
Version               : 0.2.0
In tree               : base
Status                : enabled, up (pid 7287) 7 seconds
Type                  : longrun
Description           : Start a pulseaudio session
Source                : /usr/lib/66/service/pulseaudio
Live                  : /run/66/tree/1002/base/servicedirs/pulseaudio
Dependencies          : pulseaudio-log
External dependencies : None
Optional dependencies : None
Start script          : 	execl-toc -S ${XDG_RUNTIME_DIR}/pulse/native -m 0755
                        	pulseaudio --daemonize=no
Stop script           :  pulseaudio --kill 
Environment source    : None
Environment file      : None
Log name              : pulseaudio-log
Log destination       : /home/z/.66/log/pulseaudio
Log file              : None

z@ obarunS6 ~ %
when everything else fails, rebuild the trees...

i did imply to rebuild the boot-user tree, ergo implies rebuilding user tree as well. that should still do the same thing?

what "manual" export?
i need to, in the shell, manually export XDG_RUNTIME_DIR =/run/user/1002 to get my dbus running
because svscan vars thing does not get munched in upon xinitrc is my theory
setting XDG_RUNTIME_DIR should not be necessary, since this is sourced from your ~/.66/conf/svscan@ z/ already as stated in your other post. Setting it before running startx X would not make difference coz again this is RESET and overwritten when .xinitrc (or .xsession) runs (assuming boot-user/user trees runs normally). Again, i advice to rebuild boot-use and the use trees.

whats after 66-all up anyways in your .xinitrc (or .xsession if using login manager) and what does XDG_RUNTIME_DIR shows if you do not export it manually...
udo wrote
z@ obarunS6 ~ % ls -la $HOME/.66/conf/svscan@ z/
total 12K
drwxr-xr-x 2 z users 4.0K Feb 20 07:31  ./
drwxr-xr-x 5 z users 4.0K Feb 20 07:31  ../
-rw-r--r-- 1 z users  374 Feb 20 22:31 'svscan@ z'

z@ obarunS6 [1] ~ % cat /home/z/.66/conf/svscan@ z/svscan@ z 
HOME=/home/z
LOGNAME=z
USER=z
PATH=/usr/bin:/usr/sbin:/bin:/sbin:/usr/local/bin
SHELL=/bin/zsh
DISPLAY=:0
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1002/bus
XDG_RUNTIME_DIR=/run/user/1002
XDG_CACHE_HOME=/home/z/.cache
XDG_CONFIG_HOME=/home/z/.config
XDG_DATA_HOME=/home/z/.local/share
XDG_DATA_DIRS=/home/z/.local/share:/usr/local/share:/usr/share
XDG_SESSION_CLASS=user
z@ obarunS6 ~ %
everything normal i guess. but the .xinitrc just not does it.
when i start xfce i notice dbus (eg. pulse) is not working, so i go back to the shell type just "dbus-launch" and there i get the error message (or when i type it a terminal window).
after "export XDG_RUNTIME_DIR =/run/user/1002" before starting x everything seems to work now.
10 days later
I also have the problem that there is no sound any more.

I tried to help myself by studying the discussion here, but maybe my
problems are different.

mpg123 file.mp3

produced the error message:

[src/libout123/modules/sdl.c:122] error: Couldn't open SDL audio: No available audio device
main: [src/mpg123.c:323] error: out123 error 7: failed to open device

Since both

sudo 66-intree -g|grep pulseaudio
66-intree -g|grep pulseaudio

yielded nothing, I suspected pulseaudio not started or not
even enabled.

But I got ( 3 > being my prompt):

3 >
66-start -v4 pulseaudio
66-start(src/lib66/ssexec_start.c: ssexec_start(): 260): info: pulseaudio is not enabled
3 >
66-enable pulseaudio
66-enable: fatal: unable to resolve source path of: pulseaudio

Moreover I got

3 >
66-inservice pulseaudio
66-inservice: fatal: unknown service: pulseaudio

Can anybody help me?

PS: I would also need a man page or tutorial on how to use
this forum. E.g. how to quote from other messages, how to post code, etc.
Is there anything suitable?
Bertram wroteI also have the problem that there is no sound any more.

I tried to help myself by studying the discussion here, but maybe my
problems are different.

mpg123 file.mp3

produced the error message:

[src/libout123/modules/sdl.c:122] error: Couldn't open SDL audio: No available audio device
main: [src/mpg123.c:323] error: out123 error 7: failed to open device

Since both

sudo 66-intree -g|grep pulseaudio
66-intree -g|grep pulseaudio

yielded nothing, I suspected pulseaudio not started or not
even enabled.

But I got ( 3 > being my prompt):

3 >
66-start -v4 pulseaudio
66-start(src/lib66/ssexec_start.c: ssexec_start(): 260): info: pulseaudio is not enabled
3 >
66-enable pulseaudio
66-enable: fatal: unable to resolve source path of: pulseaudio

Moreover I got

3 >
66-inservice pulseaudio
66-inservice: fatal: unknown service: pulseaudio

Can anybody help me?

PS: I would also need a man page or tutorial on how to use
this forum. E.g. how to quote from other messages, how to post code, etc.
Is there anything suitable?
pulseaudio module should be run as a "user" instead of root. So, make sure to create your user tree and enable it first. So assuming that's already done:

install pulseaudio-66serv
# pacman -S pulseaudio-66serv
enable pulseaudio module(take note, this should be done as "user", so no sudo
% 66-enable -t <user-tree> pulseaudio
that should all that is needed to enable pulseaudio (assuming all other trees are working and necessary services are running like dbus, dbus-session@ ,
Thanks a lot. Sound seems to work now.

However, the situation is very confusing, because sound worked already
in the past under apparently different conditions.

observice/pulseaudio-66serv was not installed, but it never was
(according to pacman.log).
Why is it needed now?

Moreover, I just typed
66-enable pulseaudio
omitting the suggested -t <user-tree>
and it seems to work nevertheless.

Well, I still have to learn about trees -- and all the other s6/66
stuff -- and I made a little effort this morning which left me in some
state of confusion.

I found the question

But how is a user tree created, enabled, ....

on http://wiki.obarun.org/doku.php?id=dbus_and_dm

Down the page I found

Create a user configuration tree as root, ...
# 66-tree -nE boot-user

I suppose that what's called a user configuration tree here is the
same as what higher up on the same page is just called a user tree ?
and that boot-user is the concrete name of the user tree to
be created?

Next comes

Do not forget the -E (Enable) option at tree creation to be able to start the tree at boot time.
# 66-enable -t boot-user boot-user@ oblive

Does that mean that the -E option above is a perequisite for running
successfully the 66-enable command, or is the 66-enable a substitute
for an ommitted -E option ?

The man page of 66-tree says that
with the -n option just an empty tree is created.
Now, what makes an empty tree into a user tree?
Is it the command
# 66-env -t boot-user -e nano boot-user@ oblive
which will create the file boot-user@ oblive ?

Moreover, I have a tree named boot-user with my Obarun installations.
Is it the user tree? How do I know ?
From the ...@ bf -- with bf my user name -- in its contents?
Or from the existence of the file boot-user@ bf ?

Finally, is there a difference between

66-enable pulseaudio

and

66-enable -t <user-tree> pulseaudio

or would -t <user-tree> just have added a default?
Bertram wrote Why is it needed now?
pulseaudio functionality is designed around systemd, by the same group, so its own versions are breaking dependencies and functionality as systemd changes. Otherwise either dbus or ck weren't running correctly. With alsa I've never had any problems or the need for dbus/ck/logind. Once it is set for a specific machine it is 100% reliable.
Moreover, I just typed
66-enable pulseaudio
omitting the suggested -t <user-tree>
and it seems to work nevertheless.
You can make 1000 trees, only one can be current. For an existing tree (root or user) the command: 
66-tree -c treename
makes it current.
When you don't specify a tree 66-enable/disable commands are applied to the current tree.
But how is a user tree created, enabled, ....
on http://wiki.obarun.org/doku.php?id=dbus_and_dm
Down the page I found
Create a user configuration tree as root, ...
# 66-tree -nE boot-user
I suppose that what's called a user configuration tree here is the
same as what higher up on the same page is just called a user tree ?
and that boot-user is the concrete name of the user tree to
be created?
A user tree and the boot-user tree are very separate terms. Any tree "created by the user" is referred to as a user tree.
For any user to enable trees and services as a user "root must create a tree commonly referred to in Obarun as a boot-user tree" and most importantly within this tree there is a service/module called boot-user@ , which can be configured especially for a particular user. In the past, before this became a module, there was a service called boot-user and it was the same for all users. Now it can be user specific. The names of the trees are arbitrary, you can name them differently once you understand their function.
For any "user" service to function a "user scandir" must be active, and this is handled by root by configuring the boot-user tree and services. If not, a user can create a tree but enabling and starting any services will fail.
Next comes

Do not forget the -E (Enable) option at tree creation to be able to start the tree at boot time.
# 66-enable -t boot-user boot-user@ oblive

Does that mean that the -E option above is a perequisite for running
successfully the 66-enable command, or is the 66-enable a substitute
for an ommitted -E option ?
Enabled in 66 means
for root: Once booting has completed (boot tree services complete) ALL trees that are enabled are "initiated" (# 66-intree -zg will show you different fields for enabled, initiated, default, etc.). Enable/disable is like an on/off switch, there is no middle. Either a tree is enabled or disabled. A tree that is disabled is there, ready to be started by root normally by issuing the < # 66-all -t treename up > command. Otherwise it is asleep.

for user: Once the user logs into the system, AND ONLY IF a scandir has been activated by root for that user (boot-tree --> boot-user@ username), then all "user trees" that ARE enabled, will be "initiated", meaning the services/modules active on those will attempt to start. User trees that are not-Enabled/Disabled remain asleep, till the user issues a <% 66-all -t usertreename up> command.

I believe most of what I am saying here is also covered in "intro to 66" in the wiki, 3-4 people contributed the creation of this document so it helps Obarun users in specific, to go past the state of confusion into the stage of experimentation with 66 tools.
The man page of 66-tree says that
with the -n option just an empty tree is created.
Now, what makes an empty tree into a user tree?
Simply if root creates a tree it is a root tree, if user oblive creates a tree it is oblive's tree (a user tree), the user does whatever she/he wants with it. The only thing root does for the user is create a scandir for user (ex: 1002 bob) to be able to start and stop service supervision (that is the boot-user tree created by root for the user and configured for the particular user by the boot-user@ bob module. If a scandir is not running for the user no tree, service, or module, can be supervised for the user.

Again I shouldn't copy/paste "intro to 66" here but there is a little confusion created here by the separation of Obarun and 66.
66 documentation is ONLY about 66 tools. Obarun documentation and wiki are about 66 implementation into obarun. 66 functionality is standard, but things like services, boot@ boot-user@ modules, etc. are all Obarun implementations. In Void or Antix if they officially adopt 66 the implementation may be slightly different. So not all questions about 66 can be answered by the wiki, if they are 66 specific. No questions about service files and modules can be answered by 66 documentation if they are Obarun implementations.

PLEASE suggest an alternative way that this discrepancy would be more understandable to new users.
user prompt % 
% 66-tree -n newtree    # a user tree is created named newtree
% 66-tree -E newtree    # newtree is Enabled
% 66-tree -c newtree    #  newtree is set as current -- among other user trees
% 66-tree -D newtree    # newtree is Disabled, will not start at login
% 66-tree -n othertree    # a user tree is created named othertree
% 66-tree -cE othertree    # othertree is Enabled and set as current -- newtree is no longer current, othertree is
% sudo 66-tree -ncE -S boot root2  # A ROOT tree is created, it is set a "c"urrent and is "E"nabled and will "-S"tart after boot tree completes.
% sudo 66-tree -D root  # root tree is disabled 
% sudo 66-tree -R root  # root tree is deleted
% 66-intree -zg  # will show you a summary of what "user" trees exist and what the status of trees and services is
% sudo 66-intree -zg  # will show you a summary of what "root" trees exist and what the status of trees and services is
# 66-intree -zg 
and
% sudo 66-intree -zg 
are the same, attention to the prompt  % or #
Is it the command
# 66-env -t boot-user -e nano boot-user@ oblive
which will create the file boot-user@ oblive ?
This command configures a module, both tree and an enabled module must be created in advance for this to execute.
If tree boot-user does not exist and/or boot-user@ oblive hasn't been enabled in that tree (boot-user), the command will fail.
66-env can not create any tree or service, or enable a service inside a particular tree. Both those tasks have to be done in advance for 66-env to work.
So you create boot-user tree, enable boot-user@ oblive module for user oblive, then use this command to configure the module.
It is called a module as the same basic service can be configured differently for different users.
Moreover, I have a tree named boot-user with my Obarun installations.
Is it the user tree? How do I know ?
Tree names can be anything, it can be zzz123 if you wanted. The proposed named convention through the Obarun live images and wiki documentation is that a boot-user is a "root" created tree to enable the boot-user@ oblive module and configure it.
If you run 66-intree in a root shell or using sudo in front, those are all root trees you see. If you run the same command as user you will only see user trees and services.
From the ...@ bf -- with bf my user name -- in its contents?
Or from the existence of the file boot-user@ bf ?
For the particular "obarun" module named boot-user@ -66serv for each user the root can create a different module named after the user. So in JWM -live iso it is boot-user@ oblive in a tree made by root named boot-user.
Give it a week or two and the more you play with them the more sense it will make. After a while it will be so crystal clear that you will wonder how do all those other Linux distros handle stuff like this. The answer is they don't and mostly they can't. In Obarun we can. So with this ability comes the complexity and a steep learning curve.
Finally, is there a difference between

66-enable pulseaudio

and

66-enable -t <user-tree> pulseaudio

or would -t <user-tree> just have added a default?
You can only learn by experimenting and once you mess up you can ask, and most of us do our best to share the light handed down by 66 god.
I think the answer is covered from above, but do this exercise, create 5 -n new trees. Enable some, see which one is current. Make one current. Enable a fake service in it, like make a service file in ~/.66/service/ls and have it show the contents of a directory or something dumb. A oneshot service.
If you don't specify which tree to be enabled, it automatically goes to the current one. If you have only 1 tree it is automatically current. By creating a new tree unless you specify -c to make it current, the first current remains as current.
Even if you wrote a failing service file and the service fails it will still show on user's tree as enabled, just not running. If it is a oneshot it will say up (meaning it was executed and done), down would have meant it wasnt' executed yet. 
               ├─(up,Enabled,oneshot) mount-swap
This is from boot tree and it means that when boot tree was initiated at boot, service mount-swap was executed succesfully. 
               └─(931,Enabled,classic) dhclient@ eth0
This is dhclient@ eth0 a module-type of service configured for eth0 (interface) in a tree ... and this is running and currently supervised by 66, process # (pid) is 931.

66-intree -zg is your best friend in understanding all this, testing, and diagnosing what is wrong. The -z option for color helps as your eye will catch all the read that is failing. You want to see all green. Orange means they are asleep, waiting for you to start them.
@ fungal_net
If you have only 1 tree it is automatically current.
this is not correct. You don't have any current tree by default.
Let's say with build our 66 eco-system from scratch (so no installer) 
66-tree -n very_first_tree
66-tree: info: Created successfully tree: very_first_tree
66-enable service_test
66-enable: fatal: unable to find the current tree. You must use -t options
By default, 66 do not set any tree as a default one.
Thank you, I corrected the LONG message, and I am glad someone is reading it, even if LONG!
I see, lots of misunderstandings on my side. Dear me!
Thanks a lot for all the explanations.
They helped already at first reading, but I will study them more carefully.

Powered by Obarun