When we restarted CAPM daemons, we received the Warning message to Run 'systemctl daemon-reload' to reload units. We would like to know is there any impact if we execute this Run command and why we received this message below:
Warning: mysql.service changed on disk. Run 'systemctl daemon-reload' to reload
Redirecting to /bin/systemctl start caperfcenter_sso.service
Warning: caperfcenter_sso.service changed on disk. Run 'systemctl daemon-reload' to reload units
Redirecting to /bin/systemctl start caperfcenter_devicemanager.service
Warning: caperfcenter_devicemanager.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Redirecting to /bin/systemctl start caperfcenter_eventmanager.service
Warning: caperfcenter_eventmanager.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Redirecting to /bin/systemctl start caperfcenter_console.service
Warning: caperfcenter_console.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Release : NetOps 20.2
Component : IM Reporting / Admin / Configuration
daemon-reload
Reload systemd manager configuration. This will rerun all generators (see systemd.generator(7)), reload
all unit files, and recreate the entire dependency tree. While the daemon is being reloaded, all sockets
systemd listens on behalf of user configuration will stay accessible.
This command should not be confused with the reload command.
Run 'systemctl daemon-reload'