Pass the LPIC Level 1 102-500 Questions and answers with ExamsMirror

The ulimit command is used to set or display the limitations on the system resources available to the current shell and its descendants. One of the resources that can be controlled by ulimit is the maximum size of a core file that is created when a program crashes. A core file is a snapshot of the memory and registers of a process at the time of termination, which can be used for debugging purposes. By default, the core file size limit is zero, which means no core file will be generated. To change the core file size limit, the option -c can be used with ulimit, followed by a number that represents the maximum number of blocks (usually 512 bytes) that can be written to a core file. For example, the command ulimit -c 1000 will set the core file size limit to 512000 bytes. To remove the core file size limit, the option -c can be used with ulimit, followed by unlimited. For example, the command ulimit -c unlimited will allow core files of any size to be created. References:

LPIC-1 Exam 102 Objectives, Topic 103: Linux Installation and Package Management, Subtopic 103.3: Manage shared libraries, Weight: 1, Key Knowledge Areas: Identify the location and purpose of important file and directories as defined in the FHS, Objective: Use the ulimit command to set or display limitations on the system resources available to the current shell and its descendants.

LPIC-1 Exam 102 Learning Materials, Topic 103: Linux Installation and Package Management, Subtopic 103.3: Manage shared libraries, Section 103.3.2: ulimit, Page 14-15.

 The /etc/shadow file is a text file that stores encrypted passwords, along with user name, password expiration values, and last password change date. The credential information in the shadow file is encrypted using a one-way hash function to disable decryption. The /etc/shadow file contains one entry per line for each user listed in /etc/passwd file. Each line of the /etc/shadow file contains nine comma-separated fields, and the second field is the encrypted password of the user. The password field uses the $type$salt$hashed format, where $type is the method of cryptographic hash algorithm, salt is a random string, and hashed is the result of applying the hash function to the user’s password and the salt. The /etc/shadow file is only readable by the root user, and it is used to enhance the security and control of user passwords.

The other information listed are not stored in /etc/shadow file, but in /etc/passwd file. The /etc/passwd file is a text file that contains basic information about each user account on the system. Each line of the /etc/passwd file contains seven colon-separated fields, and they are:

Username: The name of the user account.

Password: An x character indicates that the encrypted password is stored in /etc/shadow file.

User ID (UID): The numerical identifier of the user account.

Group ID (GID): The numerical identifier of the primary group of the user account.

User ID Info: The comment field that can store additional information about the user, such as full name, phone number, etc.

Home Directory: The absolute path to the user’s home directory, where the user’s personal files and settings are stored.

Shell: The absolute path to the user’s default login shell, which is the program that runs when the user logs in to the system.

References:

Understanding the /etc/shadow File | Linuxize

Understanding /etc/shadow file format on Linux - nixCraft

/etc/shadow file format | Linux#

[/etc/passwd file format | Linux#]

This command will find all the files in the /usr directory that have the user ID (UID) of 0, which is the root user, and have the permission of 4000, which is the SUID bit. The SUID bit allows the file to be executed with the privileges of the file owner, regardless of who runs it. The -uid option tests for a specific UID, and the -perm option tests for a specific permission. The + sign before the permission means that at least those bits are set; the - sign means that exactly those bits are set. The other options are either invalid or do not match the criteria. References:

LPIC-1 Exam 102 Objectives, Topic 104: Devices, Linux Filesystems, Filesystem Hierarchy Standard, 104.4 Find system files and place files in the correct location, Key Knowledge Areas: Search for files by type, size, or time

find manual page, -uid and -perm options description

Find Command in Linux with Practical Examples, Example 8: Find Files with SUID and SGID Permissions

The /etc/syslog.conf file is used to configure the syslog daemon, which handles the logging of system messages. The file consists of lines that have the following format:

selector action

The selector specifies the type and priority of the messages to be logged, and the action specifies what to do with the messages. The selector has two parts, separated by a dot: the facility and the priority. The facility indicates the source of the message, such as mail, auth, kern, etc. The priority indicates the severity of the message, such as emerg, alert, crit, err, etc. A priority can also be preceded by an equal sign (=) to match only that priority, or a minus sign (-) to match all priorities except that one.

The action can be one of the following:

A filename, starting with a slash (/), indicating the file to write the messages to.

A hostname, preceded by an at sign (@), indicating the remote host to send the messages to via UDP.

A username, indicating the user to send the messages to via wall.

An asterisk (*), indicating all logged-in users.

A pipe symbol (|), followed by a command, indicating the program to pipe the messages to.

In this question, the correct entry is D. mail.*/var/log/maillogmail.crit@logger.example.org. This entry means:

Log all mail related messages (mail.*) to the file /var/log/maillog.

Log all critical mail messages (mail.crit) to the remote host logger.example.org.

The other options are incorrect because:

Option A is missing a dot between mail and crit, and uses the wrong domain name (example.org instead of example.com).

Option B uses an invalid action (syslog://logger.example.org) that is not supported by syslog.conf.

Option C is missing a dot between mail and *.

Option E is missing dots between mail and * and between mail and crit.

References: [LPI 102-500 Exam Objectives], Topic 106.1: Maintain system time, Weight: 3. [LPI Linux Essentials Study Guide], Chapter 9: Administrative Tasks, Section 9.4: System Logging.

 The comparison operators for test that work on elements in the file system are -d and -f. The -d operator tests if a given file name refers to a directory, and returns true if it does. The -f operator tests if a given file name refers to a regular file, and returns true if it does. These operators are part of the topic 105.3: Perform basic file management, which is one of the objectives of the LPI Linux Administrator - 102 exam12. References: 1: LPI Linux Administrator - 102 (LPIC-1) 2: Exam 102 Objectives

The command journalctl is included in systemd and supports selecting messages from the systemd journal by criteria such as time or unit name. The systemd journal is a binary log file that stores system and service messages. The journalctl command can be used to view, filter, export, and manipulate the journal entries. For example, to show all messages from a specific unit, such as sshd.service, the command would be:

journalctl -u sshd.service

To show all messages from a specific time range, such as yesterday, the command would be:

journalctl --since=yesterday

The journalctl command has many options and arguments that can be used to customize the output and perform various operations on the journal. For more information, see the man page of journalctl or the official documentation1. References: [LPI 102-500 Exam Objectives], Topic 106.2: System logging, Weight: 3. [systemd-journald.service(8) — systemd — Debian unstable — Debian Manpages], Section NAME.

The ssh-agent command is a program that runs in the background and acts as a key manager for SSH. It can store multiple private keys in memory and provide them to SSH clients when needed. This way, the user does not have to enter the passphrase for each key every time they log in to another machine using SSH. The ssh-agent can also forward the authentication request to another agent running on the original machine, allowing the user to hop between different machines without re-entering the passphrase1.

To use ssh-agent, the user needs to start it and add the private keys to it using the ssh-add command. The ssh-add command can also list, delete, and lock the keys stored in the agent. The user can then use the SSH_AUTH_SOCK environment variable to connect to the agent and use the keys for authentication2.

The other commands are not related to the ssh-agent. The sshd command is the SSH server daemon that listens for incoming connections and handles the authentication and encryption. The ssh-keygen command is a tool for generating, managing, and converting SSH keys. The ssh command is the SSH client that initiates the connection to the remote machine3. References: 1: SSH Essentials: Working with SSH Servers, Clients, and Keys. 2: [ssh-agent(1) - Linux manual page]. 3: SSH command usage, options, and configuration in Linux/Unix.

 The /etc/nologin file is used to prevent all users except root from logging into the system. This file is usually created by the system administrator when the system is going down for maintenance or reboot. The file can contain a message that is displayed to the users who try to log in, explaining the reason for the system shutdown. The file is automatically removed by the system when it boots up again. References:

LPI 102-500 Exam Objectives, Topic 104: Administrative Tasks, 104.5 Manage user accounts

LPI 102-500 Study Guide, Chapter 4: User and Group Management, Section 4.3: Preventing Users from Logging In