chkconfig vs systemctl on Amazon T3 intances.

I was a bit surprised when installing Apache 2.4 on Amazon EC2 T3 instance that chkconfig did not work like it does on my T2 instances; instead you use systemctl.

Here is a bit of a conversion table for the two.

List processes
chkconfig:

# chkconfig –list
systemd:

# systemctl list-units
Enable a service
chkconfig:

# chkconfig <servicename> on
systemd:

# systemctl enable <servicename>.service
Disable a service
chkconfig:

# chkconfig <servicename> off
systemd:

# systemctl disable <servicename>.service
Start a service
chkconfig:

# service <servicename> start
systemd:

# systemctl start <servicename>.service
Stop a service
chkconfig:

# service <servicename> stop
systemd:

# systemctl stop <servicename>.service
Check the status of a service
chkconfig:

# service <servicename> status
systemd:

# systemctl status <servicename>.service

I believe this is because the Amazon T3 instances have updated Centos, Rhel and Fedora features.

If we take a peak at the operating system we see

 

 

Leave a Reply

Your email address will not be published. Required fields are marked *