Je ne suis pas un pro en systemd mais en tapant simplement "systemd static service" sur google, on tombe sur un forum archlinux où l'on peut lire la chose suivante :
Static units are those which cannot be enabled/disabled, but it doesn't mean they are always executed. They will only if another unit depends on them, or if they are manually started.
Actually, static units are simply those without an [Install] section. As enabling units means just creating a symlink to wherever [Install] mandates, those units without [Install] section cannot be enabled, as systemctl doesn't know where to place the symlink.
Of course, you can still manually create a symlink from a static unit to (for instance) /etc/systemd/system/multi-user.target.wants/, and it will be executed as any other enabled unit. But I suppose static units are not intended to be enabled in that way, and most probably you shouldn't need to do it
# They are not meant to be enabled using systemctl
Posté par chaispaquichui . En réponse au message systemd service non démarré.. Évalué à 6.
Je ne suis pas un pro en systemd mais en tapant simplement "systemd static service" sur google, on tombe sur un forum archlinux où l'on peut lire la chose suivante :
Static units are those which cannot be enabled/disabled, but it doesn't mean they are always executed. They will only if another unit depends on them, or if they are manually started.
Actually, static units are simply those without an [Install] section. As enabling units means just creating a symlink to wherever [Install] mandates, those units without [Install] section cannot be enabled, as systemctl doesn't know where to place the symlink.
Of course, you can still manually create a symlink from a static unit to (for instance) /etc/systemd/system/multi-user.target.wants/, and it will be executed as any other enabled unit. But I suppose static units are not intended to be enabled in that way, and most probably you shouldn't need to do it
Je pense que ça répond à ta question