Changes

From SME Server
Jump to navigationJump to search
m
Line 432: Line 432:     
=== Systemd current implementation ===
 
=== Systemd current implementation ===
Previously we had sysvinit services and supervised services under Deamontool and Runit.
+
Previously we had sysvinit services and supervised services under Daemontool and Runit.
   −
We are currently moving all sysvinit handled service to systemd.  
+
We are currently moving all sysvinit handled service to systemd.
   −
For services supervised with Runit, we either move them to systemd with their own unit if one is provided, or we create one which will keep the service runing under Runit
+
For services supervised with Runit, we either move them to systemd with their own unit if one is provided, or we create one which will keep the service running under Runit
   −
The idea is to stop to have the Bootstrap Console to start services.
+
The idea is to stop to have the Bootstrap Console start services.
    
==== default target: sme-server.target ====
 
==== default target: sme-server.target ====
Line 444: Line 444:     
==== system-preset ====
 
==== system-preset ====
The use of system preset is the base of our way to handle the systemd services under Koozali SME Server.
+
The use of system presets is the basis of our method of handling the systemd services under Koozali SME Server.
   −
For direct post install purpose we user a e-smith-base RPM owned file :  /usr/lib/systemd/system-preset/50-Koozali.preset
+
For direct post-install purposes we use an e-smith-base RPM owned file :  /usr/lib/systemd/system-preset/50-Koozali.preset
    
This file contains a list of service we want to have enabled or disabled.
 
This file contains a list of service we want to have enabled or disabled.
   −
Another file will take precedence without hiding it: /etc/systemd/system-preset/49-koozali.preset. This file is templated, and use the e-smith configuration db to list services that should be enabled or disabled based on admin changes.
+
Another file will take precedence without hiding it: /etc/systemd/system-preset/49-koozali.preset. This file is templated, and uses the e-smith configuration db to list services that should be enabled or disabled based on admin changes.
   −
This is important that this file is called 49-koozali.preset and not 50-Koozali.preset, so it does not hide 50-Koozali.preset content, but take precedence on it. Hence, anything not declared in 49-koozali.preset will take the state of what declare the 50 one.
+
It is important that this file is called 49-koozali.preset and not 50-Koozali.preset, so it does not hide 50-Koozali.preset content, but take precedence on it. Hence, anything not declared in 49-koozali.preset will take the state of what declare the 50 one.
    
Then we use an action script to default all we want in systemd: /etc/e-smith/events/actions/systemd-default<syntaxhighlight lang="bash">
 
Then we use an action script to default all we want in systemd: /etc/e-smith/events/actions/systemd-default<syntaxhighlight lang="bash">

Navigation menu