Logs help you understand what a system or program did. Start by gathering information rather than changing settings.
View readable log files
ls -lah /var/log | less
Depending on your system and privileges, you might find logs for authentication, network services and system messages. Names and locations differ by distribution and service.
Follow a text log
tail -n 30 /path/to/your.log
tail -f /path/to/your.log
Replace the example path. Press Ctrl+C to stop following output. Some log files are only readable by root or a privileged group.
Journal-based systems
On distributions using systemd, journalctl is commonly useful, but Slackware 15.0 does not use systemd by default. Don't assume a command from a different distro applies to your machine.
Record your investigation
uname -a
ip route
df -h
Save non-sensitive command output if you need help. Review and redact usernames, addresses, tokens and other private details before posting logs anywhere.
Troubleshooting method: observe → form one hypothesis → test it → note the result. Resist the urge to edit five files at once.