I believe it is one of the main reasons why systemd replaced init in most linux distro, to provide concurrent and parallel processing at boot.
Yeah specifically I believe systemd is better able to determine dependencies and only start the next service when its deps are all properly up and running.
Your fix is probably the correct way to do it, procd doesn't really have strict ordering other than the script filenames.
This change will probably be overwritten by a firmware update unless you build your own images so yeah, if you needed a reason to feel uncomfortable with it, there you go.
Is there any reason you need to bind to a specific address other than to force nginx only on the LAN interface? I understand this is probably a router and you may not want to rely on the firewall.
Is there any reason you need to bind to a specific address other than to force nginx only on the LAN interface?
Just the default settings, I haven't touched any nginx config at all.
I believe it is one of the main reasons why systemd replaced init in most linux distro, to provide concurrent and parallel processing at boot.
Yeah specifically I believe systemd is better able to determine dependencies and only start the next service when its deps are all properly up and running.
More replies
Your fix is probably the correct way to do it, procd doesn't really have strict ordering other than the script filenames.
This change will probably be overwritten by a firmware update unless you build your own images so yeah, if you needed a reason to feel uncomfortable with it, there you go.
Is there any reason you need to bind to a specific address other than to force nginx only on the LAN interface? I understand this is probably a router and you may not want to rely on the firewall.
Just the default settings, I haven't touched any nginx config at all.
More replies More replies