Discussion :

[bomonde]

Bonjour,

J'ai une question concernant systemctl, j'ai mis en place un script de stop/start de certains services propre à mon exploitation, à chaque reboot de serveur les services se lance automatiquement/
Ma question est la suivante: " est-il possible de scheduler plusieurs systemctl afin de lancer les relance de services les uns apres les autres car certains services ne doivent pas se lancer en meme temps ? "


Merci de vos réponses

Bonne journée

[transgohan]

Euh non on va pas lancer plusieurs gestionnaires de service ça risque de mettre la grouille partout !

Par contre tu peux indiquer à systemctl de lancer certains services après d'autres avec la configuration "After".

Extrait du man :

Before=, After=

These two settings expect a space-separated list of unit names. They configure ordering dependencies between units. If a unit foo.service contains a setting Before=bar.service and both units are being started, bar.service's start-up is delayed until foo.service has finished starting up. Note that this setting is independent of and orthogonal to the requirement dependencies as configured by Requires=, Wants= or BindsTo=. It is a common pattern to include a unit name in both the After= and Requires= options, in which case the unit listed will be started before the unit that is configured with these options. This option may be specified more than once, in which case ordering dependencies for all listed names are created. After= is the inverse of Before=, i.e. while After= ensures that the configured unit is started after the listed unit finished starting up, Before= ensures the opposite, that the configured unit is fully started up before the listed unit is started. Note that when two units with an ordering dependency between them are shut down, the inverse of the start-up order is applied. i.e. if a unit is configured with After= on another unit, the former is stopped before the latter if both are shut down. Given two units with any ordering dependency between them, if one unit is shut down and the other is started up, the shutdown is ordered before the start-up. It doesn't matter if the ordering dependency is After= or Before=, in this case. It also doesn't matter which of the two is shut down, as long as one is shut down and the other is started up. The shutdown is ordered before the start-up in all cases. If two units have no ordering dependencies between them, they are shut down or started up simultaneously, and no ordering takes place. It depends on the unit type when precisely a unit has finished starting up. Most importantly, for service units start-up is considered completed for the purpose of Before=/After= when all its configured start-up commands have been invoked and they either failed or reported start-up success.

[bomonde]

en fait j'ai ca dans mon fichier service en ce moment

Code :

Sélectionner tout - Visualiser dans une fenêtre à part

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
 
[Unit]
Description=Start/Stop host application
Requires=network.target
After=local-fs.target network.target
 
[Service]
Type=oneshot
ExecStop=/apps/scope/scripts/stopAtBoot.sh
RemainAfterExit=yes
ExecStart=/apps/scope/scripts/startAtBoot.sh
User=unix
Group=prod
 
[Install]
WantedBy=multi-user.target

le scripts stopAtboot stop des services a chaque reboot du serveur puis ensuite le startAtboot les relance jusqu'ici rien de tres technique lol
Mais j'aimerai savoir si je peux rajouter apres mon start une nouvelle ligne pour faire appeler de nouveau deux scripts de stop start , ci-dessous le script voulu, cela te semblerai bon ?

Code :

Sélectionner tout - Visualiser dans une fenêtre à part

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
 
[Unit]
Description=Start/Stop host application
Requires=network.target
After=local-fs.target network.target
 
[Service]
Type=oneshot
ExecStop=/apps/scope/scripts/stopAtBoot.sh
RemainAfterExit=yes
ExecStart=/apps/scope/scripts/startAtBoot.sh
User=unix
Group=prodExecStop=/apps/scope/scripts/stopAtunixBoot.sh
RemainAfterExit=yes
ExecStart=/apps/scope/scripts/startAtunixBoot.sh
User=test
Group=prod
 
[Install]
WantedBy=multi-user.target

Merci de vos réponses

[transgohan]

J'ai pas trop compris l'utilité de tout ça.
Pourquoi ne pas faire un script sh qui appelle tous les scripts les uns derrière les autres ?

[bomonde]

car il faut que cela s'enchaine ,

En premier le stopAtboot puis à la fin de se script le startboot s'enchaine
puis ensuite le stopAtunixBoot et a la fin de celui ci le startAtunixBoot

mais il y a une particularité, les deux premiers scripts se lancent avec le user unix et les deux suivants avec le user test

je peux faire quelque chose comme ci-dessous d'apres toi?

Code :

Sélectionner tout - Visualiser dans une fenêtre à part

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
 
[Unit]
Description=Start/Stop host application
Requires=network.target
After=local-fs.target network.target
 
[Service]
Type=oneshot
ExecStop=/apps/scope/scripts/stopAtBoot.sh
RemainAfterExit=yes
ExecStart=/apps/scope/scripts/startAtBoot.sh
User=unix
Group=prod
Group=prodExecStop=/apps/scope/scripts/stopAtunixBoot.sh
RemainAfterExit=yes
ExecStart=/apps/scope/scripts/startAtunixBoot.sh
User=test
Group=prod
 
 
[Install]
WantedBy=multi-user.target

[transgohan]

Et pourquoi ne pas faire un second service (test) qui attendra le démarrage du premier (unix) ?