The previous chapter introduced the journalctl command and its basic filtering options. This chapter goes deeper into the filtering syntax and the persistence configuration. The LFCS exam tests the _FIELD matching, the –grep option, the -o output format, the boot-time filtering, and the journald.conf settings that control whether logs survive a reboot. The critical distinction…

The previous chapters covered shell scripting and its debugging mechanisms. This chapter returns to system administration: the journalctl command, which is the interface to the systemd journal. Unlike traditional text-based log files (/var/log/syslog, /var/log/messages), the journal is a binary store. It is not read with cat, grep, or less directly. The journalctl command is the…

A script that fails silently or behaves unexpectedly is a script that needs debugging. The shell provides three mechanisms for this: set -x prints each command before executing it, set -v prints each line before parsing it, and the -n flag parses the script without executing it. Beyond these, there are the PS4 prompt customization,…

The previous chapters covered the syntax of scripts: variables, conditionals, loops, functions, and arguments. This chapter covers the behavior of a script when something goes wrong. A script without error handling fails silently. A command fails, the script continues, and the failure is masked by a later successful command. The exit code is 0, the…

The previous chapters covered positional parameters, special variables, and conditionals. This chapter focuses on the practical problem of argument parsing: how a script accepts options like -v, –verbose, or -f file, validates them, and behaves accordingly. The LFCS exam tests the getopts builtin, the manual while/case/shift pattern, and the difference between short options (-v) and…