I have one service which always times out, but slows down the boot
process. It is
/lib/systemd/system/systemd-networkd-wait-online.service. Because
many jobs wait in queue for a while, till this fails.
Also, I have a couple of services, ntpdate and proftpd which always
fail because when they try to execute named has not started yet. I
can restart them once the system is fully booted and I can login.
[1 <text/plain; US-ASCII (quoted-printable)>]Thanks. I am not using systemd-network or anything like that. I
On Fri, 27 May 2022 17:03:29 -0400, John Covici wrote:
I have one service which always times out, but slows down the boot
process. It is
/lib/systemd/system/systemd-networkd-wait-online.service. Because
many jobs wait in queue for a while, till this fails.
Are you using systemd-networkd or something else to manage your network?
Also, I have a couple of services, ntpdate and proftpd which always
fail because when they try to execute named has not started yet. I
can restart them once the system is fully booted and I can login.
You can create a drop-in to require the service to start after named, run "systemctl edit ntpdate.service" and add
[Unit]
Requires=named.service
After=named.service
That will create a drop-in file in /etc/systemd/system/ntpdate.service.d containing your additions - you can also create these files manually.
On Fri, 27 May 2022 17:49:24 -0400,
Neil Bothwick wrote:
[1 <text/plain; US-ASCII (quoted-printable)>]
On Fri, 27 May 2022 17:03:29 -0400, John Covici wrote:
I have one service which always times out, but slows down the boot process. It is
/lib/systemd/system/systemd-networkd-wait-online.service. Because
many jobs wait in queue for a while, till this fails.
Are you using systemd-networkd or something else to manage your
network?
Also, I have a couple of services, ntpdate and proftpd which always
fail because when they try to execute named has not started yet. I
can restart them once the system is fully booted and I can login.
You can create a drop-in to require the service to start after named,
run "systemctl edit ntpdate.service" and add
[Unit]
Requires=named.service
After=named.service
That will create a drop-in file inThanks. I am not using systemd-network or anything like that. I created a service called network and use the %i and links in /etc/systemd/system/multi-user-target.wants to start my two cards.
/etc/systemd/system/ntpdate.service.d containing your additions - you
can also create these files manually.
Maybe this is not the normal way, but when I first started using
systemd, this is the best I could come up with at the time.
I will try the drop-in, I had kind of forgot about them.
[...]
Thanks. I am not using systemd-network or anything like that. I created a service called network and use the %i and links in /etc/systemd/system/multi-user-target.wants to start my two cards.
Maybe this is not the normal way, but when I first started using
systemd, this is the best I could come up with at the time.
Name=enp2s0<br><br>[Network]<br>Address=<a href="http://192.168.1.1/24" target="_blank">192.168.1.1/24</a><br>Gateway=192.168.1.254<br>DNS=192.168.1.254<br></div><div><br></div><div>or with DHCP:</div><div><br></div><div># /etc/systemd/network/30-bond1.network<br>[Match]<br>Name=bond1<br><br>[Network]<br>DHCP=ipv6<br></div><div><br></div><div>Even with wpa_supplicant[1].</div><div><br></div><div>Regards.</div><div>[1] <a href="https://wiki.somlabs.com/index.php/Connecting_to_WiFi_network_using_
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 303 |
Nodes: | 16 (2 / 14) |
Uptime: | 74:51:42 |
Calls: | 6,805 |
Calls today: | 1 |
Files: | 12,327 |
Messages: | 5,400,052 |