From Fedora Project Wiki
(don't reference obsolete test cases) |
(use sudo instead of su, root user it not guaranteed to be included) |
||
(2 intermediate revisions by the same user not shown) | |||
Line 8: | Line 8: | ||
|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| | ## {{command|sudo journalctl -aeb}} | ||
# If rsyslog is installed (for example, on the Server | # If rsyslog is installed (for example, on the Server Edition), check: | ||
## {{command| | ## {{command|sudo tail /var/log/secure}} | ||
|results= | |results= |
Latest revision as of 10:31, 31 May 2017
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:
sudo journalctl -aeb
- If rsyslog is installed (for example, on the Server Edition), check:
sudo 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.