Recent disruptions to two undersea internet cables in the Baltic Sea have yet again...
2.4 Starting, stopping and getting status of IRP components
In order to determine the status of IRP components or to start, stop and restart them standard Linux utilities are used.
Critical errors preventing startup of a particular component are logged to console. Details can be obtained from logs stored in /var/log/irp/ directory.
Managing software components in OS with systemd #
Starting single component:
systemctl start explorer
Multiple components separated by space can be listed
Stopping single component:
systemctl stop explorer
Multiple components separated by space can be listed
Starting all components:
systemctl start irp.target
This also starts all prerequisites
Stopping all components:
systemctl start irp-shutdown.target
Stopping all components except bgpd:
systemctl start irp-shutdown-except-bgpd.target
Restarting all components:
systemctl start irp-shutdown.target
systemctl start irp.target
Obtaining overall status of all components:
systemctl list-dependencies irp.target
Individual statuses can be checked by executing command
systemctl status component_name