SystemD generates a drop-in file to work with these legacy init scripts, so for this network one, it generates:
# systemctl cat network
# /run/systemd/generator.late/network.service
# Automatically generated by systemd-sysv-generator
[Unit]
Documentation=man:systemd-sysv-generator(8)
SourcePath=/etc/rc.d/init.d/network
Description=LSB: Bring up/down networking
Before=network-online.target
Before=network.target
After=iptables.service
After=ip6tables.service
After=NetworkManager-wait-online.service
After=NetworkManager.service
After=network-pre.target
Wants=network-online.target
Wants=network.target
[Service]
Type=forking
Restart=no
TimeoutSec=5min
IgnoreSIGPIPE=no
KillMode=process
GuessMainPID=no
RemainAfterExit=yes
SuccessExitStatus=5 6
ExecStart=/etc/rc.d/init.d/network start
ExecStop=/etc/rc.d/init.d/network stop
The warning is just a symptom of the network-scripts being a legacy service that should really be removed. So systemd generates the .service file for the legacy sysvinit script using the sysv-generator and then warns users about it.
Nothing to worry about in your case.
Brendan Shephard
Senior Software Engineer
Red Hat Australia
On 13 Jan 2025, at 17:42, jordan@olinsolutions.com wrote:
Thank you @brendan! That was it!!
I cannot tell you how many days I have searched and experimented to get past this (even tried systemd-networkd to no avail).
One small thing, CentOS Stream 9 does give me the "SysV service '/etc/rc.d/init.d/network' lacks a native systemd unit file." every time the service is restarted. Do you know where I can find an equivalent to drop in and eliminate that warning? It looks like it is supposed to be generating one, but that apparently does not work.
Regardless, thank you again.
- Jordan.
_______________________________________________
users mailing list -- users@lists.rdoproject.org
To unsubscribe send an email to users-leave@lists.rdoproject.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
To unsubscribe: %(_internal_name)s-unsubscribe@%(host_name)s