···

       
109
       
 
       


     

       
110
       
 
       
Different tools take different approach to solve that issue there. `systemd`

     

       
111
       
 
       
take approach that is derived from `launchd` - do not do stuff, that is not

     

       
112
       
-
       
needed. It achieved that by merging D-Bus into the `systemd` itself, and then

     

       
113
       
-
       
making all service to be D-Bus daemons (which are started on request), and

     

       
114
       
-
       
additionally it provides a bunch of triggers for that daemons. We can trigger on

     

       
115
       
-
       
action of other services (obviously), but also on stuff like socket activity,

     

       
116
       
-
       
path creation/modification, mounts, connection or disconnection of device,

     

       
117
       
-
       
time events, etc.

     

       
118
       
 
       


     

       
119
       
 
       
---

     

       
120
       
 
       


     

···

       
109
       
 
       


     

       
110
       
 
       
Different tools take different approach to solve that issue there. `systemd`

     

       
111
       
 
       
take approach that is derived from `launchd` - do not do stuff, that is not

     

       
112
       
+
       
needed. We can trigger on action of other services (obviously), but also on

     

       
113
       
+
       
stuff like socket activity, path creation/modification, mounts, connection or

     

       
114
       
+
       
disconnection of device, time events, etc.

     

       
0
       
 
       

     

       
0
       
 
       

     

       
0
       
 
       

     

       
115
       
 
       


     

       
116
       
 
       
---

     

       
117