WEBVTT

00:03.070 --> 00:08.470
Let's take a look at how to control the Engine X service using the command line interface in Linux.

00:08.470 --> 00:14.020
It's important to note that to run commands that require root privileges, you need to either be logged

00:14.020 --> 00:17.710
in as a root user or preface the command with sudo.

00:17.980 --> 00:21.490
The status of the engine X service can be checked using the system.

00:21.520 --> 00:24.130
CTL status engine X command.

00:24.130 --> 00:30.820
The default output uses a pager, but the no pager switch can be used to get the complete output without

00:30.820 --> 00:33.790
having to type Q to end the status report.

00:33.910 --> 00:41.770
The system CTL start engine X and sys CTL Stop Engine X commands can be used to start and stop the Engine

00:41.770 --> 00:43.360
X service respectively.

00:43.600 --> 00:51.070
The system CTL is active Engine X command can be used to verify if the start or stop command ran successfully.

00:51.070 --> 00:57.940
So let's run some commands on my demo system to become the route user will type pseudo su to check the

00:57.940 --> 01:05.170
status of engine X will type system CTL status engine x to check the status of engine X without a pager

01:05.170 --> 01:05.740
system.

01:05.770 --> 01:14.710
CTL No pager status engine X to start engine x We type system CTL Start Engine X to Stop Engine X system

01:14.740 --> 01:16.900
CTL Stop Engine X to check.

01:16.900 --> 01:20.200
If Engine X is active, we'll use the following command system.

01:20.230 --> 01:22.330
CTL is Active Engine X.