From Fedora Project Wiki
(note that service other than sshd can be tested if desired) |
(Added crond as cloud example) |
||
Line 6: | Line 6: | ||
# Perform an installation of the Fedora release you wish to test, making as few choices as possible and making the most obvious and simple choices where choice is required | # Perform an installation of the Fedora release you wish to test, making as few choices as possible and making the most obvious and simple choices where choice is required | ||
|actions= | |actions= | ||
{{admon/note|Service used for testing|You may use another service for testing if necessary (for instance, testing Fedora Cloud images remotely, where disabling sshd would prevent you accessing the system). Ensure it is a service which works reliably - this is a test of the service management mechanism, not of the particular service.}} | {{admon/note|Service used for testing|You may use another service for testing if necessary (for instance, testing Fedora Cloud images remotely, where disabling sshd would prevent you accessing the system). Ensure it is a service which works reliably (like crond) - this is a test of the service management mechanism, not of the particular service.}} | ||
# Log in to the installed system | # Log in to the installed system | ||
# In a console, run the following commands: | # In a console, run the following commands: |
Revision as of 10:08, 1 November 2014
Description
This test case tests whether starting, stopping, enabling and disabling system services works as expected.
Setup
- Perform an installation of the Fedora release you wish to test, making as few choices as possible and making the most obvious and simple choices where choice is required
How to test
- Log in to the installed system
- In a console, run the following commands:
su -c 'systemctl stop sshd.service'
su -c 'systemctl disable sshd.service'
- Now reboot. Log in again, and run the following commands:
su -c 'systemctl status sshd.service'
ps aux | grep sshd
su -c 'systemctl start sshd.service'
su -c 'systemctl status sshd.service'
ps aux | grep sshd
su -c 'systemctl stop sshd.service'
su -c 'systemctl status sshd.service'
ps aux | grep sshd
su -c 'systemctl enable sshd.service'
- Now reboot. Log in again, and run the following commands:
su -c 'systemctl status sshd.service'
ps aux | grep sshd
su -c 'systemctl disable sshd.service'
- Now reboot. Log in again, and run the following commands:
su -c 'systemctl status sshd.service'
ps aux | grep sshd
Expected Results
- Each time they appear, the commands
su -c 'systemctl status sshd.service'
andps aux | grep sshd
check whether the service is running. The expected results, in order, are:- Disabled and inactive (not running)
- Disabled but active (running)
- Disabled and inactive (not running)
- Enabled and active (running)
- Disabled and inactive (not running)