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

The command userdel --force --remove bob is used to delete the user account named bob and all its associated files. The --force option forces the removal of the user account, even if the user is still logged in. The --remove option forces userdel to remove the user’s home directory and mail spool, even if another user uses the same home directory or if the mail spool is not owned by the specified user12. Therefore, options A and B are true regarding this command.

The other options are not true because:

Option C is false because the locate database is not updated by the userdel command. The locate database is updated by the updatedb command, which is usually run by cron as a scheduled job3.

Option D is false because the userdel command does not remove all files owned by bob from all mounted filesystems. The userdel command only removes the user’s home directory and mail spool, and it does not search for and delete the user files located in other file systems. You have to search for and delete the files manually1.

Option E is false because the userdel command does not delete the group with the same name as the user, unless the USERGROUPS_ENAB parameter is set to yes in the /etc/login.defs file and the group has no other members14.

References:

How to Delete/Remove Users in Linux (userdel Command) | Linuxize

userdel(8) — Linux manual page

updatedb(8) — Linux manual page

Understanding the /etc/login.defs File | Linuxize

The crontab file format consists of six fields: minute, hour, day of month, month, day of week, and command. The user-specific crontab files have the same format as the global /etc/crontab file, except that they do not have the username field. The username field is only present in the system-wide crontab files and specifies which user will run the cron job. The year field is not a valid crontab field and is not supported by cron. References:

Scheduling Cron Jobs with Crontab | Linuxize

Crontab Explained in Linux [With Examples]

The chage command can change the following parameters related to user password expiry and aging:

The last password change date (-d or --lastday option)

The password expiry date (-E or --expiredate option)

The minimum number of days between password changes (-m or --mindays option)

The maximum number of days during which a password is valid (-M or --maxdays option)

The number of days of warning before password expires (-W or --warndays option)

The chage command cannot change the number of days of inactivity after a password has expired before the account is locked. This parameter is controlled by the -I or --inactive option of the usermod command, which modifies the user account information. The chage command only displays the current value of this parameter, but does not allow changing it. References:

chage command in Linux with examples - GeeksforGeeks

10 chage command examples in Linux [Cheat Sheet] - GoLinuxCloud

How to Use the Chage Command in Linux – TecAdmin

How to Manage User Password Expiration and Aging in Linux - Tecmint

Linux UIDs (user identifiers) are numbers that are used to identify users and groups on a Linux system. Each user and group has a unique UID and GID (group identifier) respectively. The UID 0 is always reserved for the root or superuser account, which has full privileges to access and modify the system. The UIDs lower than 100 (or 1000 on some modern systems) are typically reserved for system accounts, which are used by various services and daemons that run on the system. These accounts are not meant for human users, but for specific purposes such as managing files, processes, network, security, etc. For example, some common system accounts are bin, daemon, mail, sshd, etc. The UIDs higher than 100 (or 1000) are usually allocated for regular user accounts, which have limited privileges and can be created and deleted by the system administrator. The system accounts are defined in the /etc/passwd file, which contains the username, UID, GID, home directory, shell, and other information for each account12345. References: 1: Linux User Management - Tecmint 2: What are the well-known UIDs? - Stack Overflow 3: user ID less than 1000 on CentOS 7 - Unix & Linux Stack Exchange 4: Recommended GID for users group in Linux (100 or 1000)? - Unix & Linux Stack Exchange 5: What is the conventional purpose of Linux UIDs that are lower than 100? - VCE Guide

The locale setting of the operating system is a set of environmental variables that defines the language, country, and character encoding settings (or any other special variant preferences) for the applications and shell session on a Linux system12. The locale setting usually consists of at least a language code and a country/region code, such as en_US for English (United States) or fr_FR for French (France). The locale setting also affects things such as the currency symbol, the thousands separator, the decimal point, the date and time format, the collation order, the paper size, the telephone number format, and many other values formatted in accordance with the language or region/country12. However, the timezone is not contained in the locale setting of the operating system. The timezone is a separate setting that determines the local time of the system based on the offset from the Coordinated Universal Time (UTC) and the daylight saving time (DST) rules. The timezone can be different from the country/region code in the locale setting, for example, a user can have a locale setting of en_US but a timezone of Asia/Kolkata. The timezone can be viewed and modified by using the date, timedatectl, or tzselect commands . References: 12

 The batch command is similar to the at command, except that it executes commands when the system load levels permit; in other words, when the load average drops below 1.5, or the value specified in the invocation of atd1. The at command allows us to schedule jobs using any of two commands: at and batch. While at runs commands at our specified time, batch runs commands when our system’s load average is below 0.82. Both commands read commands from standard input or a specified file, and both commands send the output of the commands to the user by mail1. Therefore, the main difference between them is the time of execution: at runs at a fixed time, while batch runs when the system is idle. References: 1: Linux At, Batch, Atq, Atrm Command Help and Examples - Computer Hope 2: The “at” Command in Linux | Baeldung on Linux

The /etc/at.deny file is a file that contains a list of users who are not allowed to use the at command to schedule jobs. If the file exists, any user who is not in the /etc/at.allow file and is in the /etc/at.deny file will be denied access to the at command. To prevent a specific user from scheduling tasks with at, the administrator can simply add the user’s name to the /etc/at.deny file. For example, to prevent the user bob from using the at command, the administrator can use the following command:

echo “bob” | sudo tee -a /etc/at.deny

The other options are not correct. The /etc/at.allow file is a file that contains a list of users who are allowed to use the at command. Adding a user to this file will not prevent them from scheduling tasks with at. The /etc/atd.conf file is a configuration file for the at daemon, which does not have a [deny] section. Adding a user to this file will not affect their access to the at command. The nojobs group is not a predefined group in Linux, and adding a user to this group will not prevent them from scheduling tasks with at. The atd command does not have a --deny option, and running this command will not prevent a user from scheduling tasks with at. References:

at Command in Linux with Examples - GeeksforGeeks

How to Use the Linux at Command {9 Examples} - phoenixNAP

at(1) - Linux man page

The /etc/localtime file is used to configure the system-wide timezone of the local system that is used by applications for presentation to the user. It should be either a symlink to or a copy of a timezone information file that contains the binary data for the configured timezone. The timezone information files are located under /usr/share/zoneinfo/ and are named after the geographic regions and cities, such as Europe/Berlin or Etc/UTC. The timezone identifier is extracted from the symlink target name of /etc/localtime, so it is recommended to use a symlink rather than a copy. The timezone can be changed by using the timedatectl command or by creating a new symlink to the desired timezone file123. References:

How to Set or Change the Time Zone in Linux | Linuxize

localtime(5) - Linux manual page - man7.org

localtime(5) — Arch manual pages

 The correct crontab entry to execute the script chklog three times per month between 3 p.m. and 5 p.m. is:

3 15,16,17 * * * chklog

The crontab entry has five fields that specify the time and frequency of the job, followed by the command or script to be executed. The fields are:

Minute: the minute of the hour when the job should run, from 0 to 59

Hour: the hour of the day when the job should run, from 0 to 23 (in 24-hour format)

Day of month: the day of the month when the job should run, from 1 to 31

Month: the month of the year when the job should run, from 1 to 12

Day of week: the day of the week when the job should run, from 0 to 6 (where 0 and 7 are Sunday)

The asterisk (*) means any value, and the comma (,) means a list of values. Therefore, the crontab entry above means:

Run the job at the 3rd minute of the hour

Run the job at the 15th, 16th, and 17th hour of the day (which are 3 p.m., 4 p.m., and 5 p.m.)

Run the job on any day of the month

Run the job on any month of the year

Run the job on any day of the week

This will execute the script chklog three times per day, every day of the month, and every month of the year, which is equivalent to three times per month.

The other options are incorrect because:

A. This will run the job at any minute of the hour, but only at the 3rd, 4th, and 5th hour of the day (which are 3 a.m., 4 a.m., and 5 a.m.), and only on the 1st day of the month.

B. This will run the job at the 3rd minute of the hour, but only at the 3rd, 4th, and 5th hour of the day (which are 3 a.m., 4 a.m., and 5 a.m.), and only on the 1st day of the month.

D. This will run the job at the 0th minute of the hour (which is the top of the hour), but only at the 15th, 16th, and 17th hour of the day (which are 3 p.m., 4 p.m., and 5 p.m.), and only on the 1st day of the month.

E. This will run the job at any minute of the hour, but only at the 15th, 16th, and 17th hour of the day (which are 3 p.m., 4 p.m., and 5 p.m.), and only on the 1st day of the month.

References:

Crontab Explained in Linux [With Examples]

‘crontab’ in Linux with Examples - GeeksforGeeks

Linux Crontab Command Help and Examples - Computer Hope

Crontab in Linux with 20 Useful Examples to Schedule Jobs - TecAdmin

Linux crontab tutorial with Examples - Linux Tutorials - Learn Linux …

 The /etc/crontab file is the system-wide crontab file that can be edited only by root. It has a different format from the normal crontab files that can be edited by individual users using the crontab command. The differences are:

The /etc/crontab file can specify a year field as the sixth field in a cron entry. This allows for scheduling jobs that run only in specific years. The normal crontab files do not have a year field and assume the current year for all entries.

The /etc/crontab file has a user field as the seventh field in a cron entry. This allows for running commands as different users from the crontab owner (root). The normal crontab files do not have a user field and run commands as the crontab owner.

The /etc/crontab file does not need to be installed with the crontab command. It is read by the cron daemon automatically. The normal crontab files need to be installed with the crontab command to be recognized by the cron daemon.

The /etc/crontab file and the normal crontab files both allow for environment variable substitution. However, the /etc/crontab file sets some default environment variables such as SHELL, PATH, MAILTO, and HOME, which can be overridden by entries in the file. The normal crontab files inherit the environment variables from the cron daemon, which are usually minimal.

References:

crontab(5) - Linux manual page

Linux Crontab Format

How to schedule a task using Linux crontab (/etc/crontab) file

/etc/crontab - Linux Bash Shell Scripting Tutorial Wiki