From Fedora Project Wiki
No edit summary |
m (since we speak about last entries, automatically scroll to the end) |
||
(2 intermediate revisions by 2 users not shown) | |||
Line 4: | Line 4: | ||
|description=This test case tests if system logging infrastructure is available and working as expected. | |description=This test case tests if system logging infrastructure is available and working as expected. | ||
|setup= | |setup= | ||
# Install Fedora | # Install Fedora according to [[QA:Testcase_Boot_default_install]], using one of the release-blocking media (e.g. Workstation live image or Server DVD). | ||
# If necessary, reboot your system after the installation. | # If necessary, reboot your system after the installation. | ||
|actions= | |actions= | ||
# If you are using a graphical environment, open a terminal window. | # If you are using a graphical environment, open a terminal window. | ||
# Check if system logging facility is working | # Check if system logging facility is working: | ||
## {{command| su -c 'journalctl - | ## {{command| su -c 'journalctl -aeb'}} | ||
# If rsyslog is installed (for example, on the Server | # If rsyslog is installed (for example, on the Server Edition), check: | ||
## {{command| su -c 'tail /var/log/secure'}} | ## {{command| su -c 'tail /var/log/secure'}} | ||
Revision as of 11:45, 23 March 2016
Description
This test case tests if system logging infrastructure is available and working as expected.
Setup
- Install Fedora according to QA:Testcase_Boot_default_install, using one of the release-blocking media (e.g. Workstation live image or Server DVD).
- If necessary, reboot your system after the installation.
How to test
- If you are using a graphical environment, open a terminal window.
- Check if system logging facility is working:
su -c 'journalctl -aeb'
- If rsyslog is installed (for example, on the Server Edition), check:
su -c 'tail /var/log/secure'
Expected Results
- Log files should not be empty.
- The last entries in logs should correspond to the current date and time.