Get Certified: Proven Methods to Pass the LPI 102-500 Exam

The date command is used to display and set the system date and time. It can also be used to print the time in different formats and calculate future and past dates. The date command has the following syntax:

date [option]... [+format]

The format controls begin with the % symbol and are substituted by their current values. For example, to display the current year, month, and day, we can use the following command:

date +"Year: %Y, Month: %m, Day: %d"

To set the system clock manually, we can use the --set or -s option followed by the date and time string. For example, to set the date and time to 5:30 PM, May 13, 2010, we can use the following command:

date --set="20100513 05:30"

The other tasks are not possible with the date command because:

• Synchronize the hardware and system clocks: The date command cannot synchronize the hardware and system clocks. To do this, we need to use the hwclock command, which can read or set the hardware clock, and also synchronize it with the system clock.
• Set the hardware clock: The date command cannot set the hardware clock. To do this, we need to use the hwclock command with the --systohc or -w option, which will copy the system time to the hardware clock.
• Update the time via NTP: The date command cannot update the time via NTP (Network Time Protocol). To do this, we need to use the ntpdate command, which will query an NTP server and set the system clock accordingly.

References:

• Date Command in Linux: How to Set, Change, Format and Display Date
• date command in Linux with examples - GeeksforGeeks
• Date Command in Linux | Linuxize

The lpr command is a legacy program provided by CUPS for sending files to the printer queues on the command line. It is one of the Berkeley (lpr) printing commands that CUPS supports for compatibility with other Unix-like systems. The lpr command accepts one or more filenames as arguments and sends them to the default or specified printer. It also supports several options to control the printing process, such as the number of copies, the page size, the orientation, and the priority. The lpr command is equivalent to the lp command, which is one of the System V (lp) printing commands that CUPS also supports. However, the lp command has more options and features than the lpr command, and is recommended for use with CUPS. References:

• Command-Line Printing and Options - CUPS
• Command-Line Printer Administration - CUPS
• Linux cups tutorial for beginners - Linux Tutorials - Learn Linux …
• CUPS Command-Line Utilities - Configuring and Managing … - Oracle

 The logrotate command is a tool for rotating, compressing, and mailing system logs. It is designed to ease the administration of systems that generate large numbers of log files. It allows automatic rotation, compression, removal, and mailing of log files. Each log file may be handled daily, weekly, monthly, or when it grows too large. Normally, logrotate is run as a daily cron job1. The logrotate command reads the configuration files specified on the command line or in the /etc/logrotate.conf and /etc/logrotate.d directories. These configuration files can set global options and specify log files to rotate and how to handle them. For example, the compress option enables compression of old log files, the mail option sends the log files to a specified email address before being rotated, and the rotate option sets the number of log files to keep12. The logrotate command is part of the LPI’s multi-level Linux professional certification program, and it is covered in the topic 106.1 System logging of the exam 102 objectives3. References: 1: logrotate(8) - Linux man page 2: logrotate command in Linux with examples - Linux command line tutorial 3: Exam 102 Objectives

• auth: Security and authorization messages, such as login failures or sudo usage12.
• authpriv: Same as auth, but used for private security messages that should not be available to all users12.
• cron: Messages from the cron daemon, such as scheduled jobs or errors12.
• daemon: Messages from system daemons, such as sshd or ntpd12.
• kern: Messages from the kernel, such as boot messages or hardware errors12.
• lpr: Messages from the line printer subsystem, such as print jobs or errors12.
• mail: Messages from the mail subsystem, such as sendmail or postfix12.
• news: Messages from the network news subsystem, such as news servers or clients12.
• syslog: Messages generated internally by the syslog daemon, such as configuration errors or restarts12.
• user: Messages from user-level processes, such as applications or scripts12.
• uucp: Messages from the Unix-to-Unix copy subsystem, such as file transfers or errors12.
• local0 to local7: Custom facilities that are not used by any system processes and can be assigned to user applications or scripts123.

Therefore, the correct answers are A. local7 and B. mail, as they are both valid syslog facilities. The other options are not syslog facilities and are either made up (C. advanced and E. remote) or refer to a specific process rather than a category of messages (D. postmaster).

References: 1: Prepare for LPIC-1 exam 2 - topic 108.2: System logging - IBM Developer Tutorial 2: 108.2 System logging - Linux Professional Institute Certification Programs 3: What is the local6 (and all other local#) facilities in syslog?

The Network Time Protocol (NTP) is a protocol that enables the accurate synchronization of time and date information across networked computer systems. NTP uses a hierarchical system of time servers, where each server has a stratum level that indicates its distance from the primary reference source. The primary reference source is usually an atomic clock or a GPS receiver, which provides the Coordinated Universal Time (UTC). The NTP clients are the computer systems that want to synchronize their system clocks with the UTC. The system clock is a software clock that runs in the kernel and keeps track of the current time and date. The system clock can be influenced by various factors, such as the hardware clock, the CPU frequency, the temperature, the load, and the network latency. These factors can cause the system clock to drift or skew from the UTC, resulting in inaccurate timekeeping. A NTP client observes and corrects the skew in time between the system clock and the reference clock, which is the clock of the NTP server that the client is connected to. The NTP client periodically sends requests to the NTP server and receives the server’s time stamps. The NTP client then calculates the offset and the round-trip delay between its system clock and the reference clock, and adjusts its system clock accordingly. The NTP client can also use multiple NTP servers and apply algorithms to select the best one and filter out outliers. The NTP client can also discipline the system clock by using a feedback loop that controls the clock frequency and reduces the clock drift. By using NTP, the system clock can achieve a high accuracy and precision, usually within a few milliseconds or microseconds of the UTC123.

The other options are not correct. The skew in time between the system clock and the hardware clock is not observed and corrected by a NTP client, but by a separate utility called hwclock, which can read and set the hardware clock. The hardware clock is a battery-powered device that keeps time even when the system is powered off. The hardware clock is usually less accurate than the system clock, and can be synchronized with the system clock at boot or shutdown time. The changes in the time zone of the current computer’s location are not observed and corrected by a NTP client, but by a configuration tool called timedatectl, which can set the system time zone and other parameters. The time zone is a geographical region that has a uniform standard time and date. The time zone does not affect the system clock, which always keeps the UTC, but only the display of the local time and date for the user. The adjustments needed to support Daylight Saving Time (DST) are not observed and corrected by a NTP client, but by the system’s time zone database, which contains the rules and transitions for DST. DST is a practice of advancing the clocks by one hour during summer months to make better use of daylight. DST is not observed in all regions and countries, and can vary in start and end dates. The system’s time zone database is updated regularly to reflect the changes in DST rules, and can be applied to the system clock to calculate the correct local time and date. References: 1: Network Time Protocol - Wikipedia 2: How NTP Works - NTP Pool Project 3: How To Set Up Time Synchronization on Ubuntu 20.042 : hwclock(8) - Linux manual page : timedatectl(1) - Linux manual page : Daylight saving time - Wikipedia