gnunux/dataset
1
0
Fork 0
forked from stove/dataset
Code Issues Pull requests Projects Releases Wiki Activity

enhancement(host): modprobe@ and resolvconf-pull-resolved services are restarted when a machine is started

Browse source 
By default, systemd don't want to (re)start too quickly. This make unecessary errors in log.

close #1
This commit is contained in:
egarette@silique.fr 2023-06-29 18:28:16 +02:00
parent 21c86b0e97
commit cc533f69bb
4 changed files with 10 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
seed/host-systemd-machined/dictionaries/21_machined.xml
View file

@ -24,6 +24,12 @@
<file engine="ansible">/etc/sysctl.d/90-risotto.conf</file> <file engine="ansible">/etc/sysctl.d/90-risotto.conf</file>
<file engine="ansible" file_type="variable" source="dhcp.network" variable="interface_names">host_network_filename</file> <file engine="ansible" file_type="variable" source="dhcp.network" variable="interface_names">host_network_filename</file>
</service> </service>
<service name="modprobe@">
<override/>
</service>
<service name="resolvconf-pull-resolved">
<override/>
</service>
<service name="vector" servicelist="vector"> <service name="vector" servicelist="vector">
<file engine="ansible">/etc/vector/vector.toml</file> <file engine="ansible">/etc/vector/vector.toml</file>
</service> </service>

2
seed/host-systemd-machined/templates/modprobe@.service Normal file
View file

@ -0,0 +1,2 @@
[Unit]
StartLimitIntervalSec=0

2
seed/host-systemd-machined/templates/resolvconf-pull-resolved.service Normal file
View file

@ -0,0 +1,2 @@
[Unit]
StartLimitIntervalSec=0

0
seed/redis/extras/accounts/00_accounts.xml
View file