RH134 - ch02s08

In this exercise, you will configure systemd-tmpfiles in order to change how quickly it removes temporary files from /tmp, and also to periodically purge files from another directory.

Outcomes

You should be able to:

Configure systemd-tmpfiles to remove unused temporary files from /tmp.
Configure systemd-tmpfiles to periodically purge files from another directory.

On workstation, run lab scheduling-tempfiles start to start the exercise. This script creates the necessary files and ensures that the environment is set up correctly.

[student@workstation ~]$ lab scheduling-tempfiles start

From workstation, open an SSH session to servera as student.

[student@workstation ~]$ ssh student@servera
...output omitted...
[student@servera ~]$

Configure systemd-tmpfiles to clean the /tmp directory so that it does not contain files that that have not been used in the last five days. Ensure that the configuration does not get overwritten by any package update.
1. Use the sudo -i command to switch to the root user.
```
[student@servera ~]$ sudo -i
[sudo] password for student: student
[root@servera ~]# 
```
2. Copy /usr/lib/tmpfiles.d/tmp.conf to /etc/tmpfiles.d/tmp.conf.
```
[root@servera ~]# cp /usr/lib/tmpfiles.d/tmp.conf \
/etc/tmpfiles.d/tmp.conf
```
3. Search for the configuration line in /etc/tmpfiles.d/tmp.conf that applies to the /tmp directory. Replace the existing age of the temporary files in that configuration line with the new age of 5 days. Remove all the other lines from the file including the commented ones. You can use the vim /etc/tmpfiles.d/tmp.conf command to edit the configuration file. The /etc/tmpfiles.d/tmp.conf file should appear as follows:
```
q /tmp 1777 root root 5d
```
  In the preceding configuration, the q type is identical to d and instructs systemd-tmpfiles to create the /tmp directory if it does not exist. The directory must have the octal permissions set to 1777. Both the owning user and group of /tmp must be root. The /tmp directory must be free from the temporary files which are unused in the last five days.
4. Use the systemd-tmpfiles --clean command to verify that the /etc/tmpfiles.d/tmp.conf file contains the correct configuration.
```
[root@servera ~]# systemd-tmpfiles --clean /etc/tmpfiles.d/tmp.conf
```
  Because the preceding command did not return any errors, it confirms that the configuration settings are correct.
Add a new configuration that ensures that the /run/momentary directory exists with user and group ownership set to root. The octal permissions for the directory must be 0700. The configuration should purge any file in this directory that remains unused in the last 30 seconds.
1. Create the file called /etc/tmpfiles.d/momentary.conf with the following content. You can use the vim /etc/tmpfiles.d/momentary.conf command to create the configuration file.
```
d /run/momentary 0700 root root 30s
```
  The preceding configuration causes systemd-tmpfiles to ensure that the /run/momentary directory exists with its octal permissions set to 0700. The user and group ownership of /run/momentary must be root. Any file in this directory that remains unused in the last 30 seconds must be purged.
2. Use the systemd-tmpfiles --create command to verify that the /etc/tmpfiles.d/momentary.conf file contains the appropriate configuration. The command creates the /run/momentary directory if it does not exist.
```
[root@servera ~]# systemd-tmpfiles --create \
/etc/tmpfiles.d/momentary.conf
```
  Because the preceding command did not return any errors, it confirms that the configuration settings are correct.
3. Use the ls command to verify that the /run/momentary directory is created with the appropriate permissions, owner, and group owner.
```
[root@servera ~]# ls -ld /run/momentary
drwx------. 2 root root 40 Mar 21 16:39 /run/momentary
```
  Notice that the octal permission set of /run/momentary is 0700 and that the user and group ownership are set to root.
Verify that any file under the /run/momentary directory, unused in the last 30 seconds, is removed, based on the systemd-tmpfiles configuration for the directory.
1. Use the touch command to create a file called /run/momentary/testfile.
```
[root@servera ~]# touch /run/momentary/testfile
```
2. Use the sleep command to configure your shell prompt not to return for 30 seconds.
```
[root@servera ~]# sleep 30
            
```
3. After your shell prompt returns, use the systemd-tmpfiles --clean command to clean stale files from /run/momentary, based on the rule mentioned in /etc/tmpfiles.d/momentary.conf.
```
[root@servera ~]# systemd-tmpfiles --clean \
/etc/tmpfiles.d/momentary.conf
```
  The preceding command removes /run/momentary/testfile because the file remained unused for 30 seconds and should have been removed based on the rule mentioned in /etc/tmpfiles.d/momentary.conf.
4. Use the ls -l command to verify that the /run/momentary/testfile file does not exist.
```
[root@servera ~]# ls -l /run/momentary/testfile
ls: cannot access '/run/momentary/testfile': No such file or directory
```
5. Exit the root user's shell and log out of servera.
```
[root@servera ~]# exit
logout
[student@servera ~]$ exit
logout
Connection to servera closed.
[student@workstation ~]$ 
```

Finish

On workstation, run lab scheduling-tempfiles finish to complete this exercise. This script deletes the files created throughout the exercise and ensures that the environment is clean.

[student@workstation ~]$ lab scheduling-tempfiles finish

This concludes the guided exercise.

Discuss Red Hat System Administration II

Go to community

Is It possible to reset root password when the system is on multi-user.target?

jennifer1987

27 lip 2023

Hi thereWell, i have a question, Is It possible to reset root password when the system is on multi-user.target? I was not be able to found a foro o some information related with this and another question that I have, If the grub menu dont show up, is it posible to reset the root password?

991

Red Hat System Administration II (RH134)

Haley_Ruccio

21 lip 2023

Build the skills to perform the key tasks needed to become a full-time Linux administratorRed Hat System Administration II (RH134) is the second part of the RHCSA training track for IT professionals who have already attended Red Hat System Administration I. The course goes deeper into core Linux system administration skills in storage configuration and management, installation and deployment of Red Hat Enterprise Linux, management of security features such as SELinux, control of recurring system tasks, management of the boot process and troubleshooting, basic system tuning, and command-line automation and productivity. This course assumes that students have attended Red Hat System Administration I (RH124).Experienced Linux administrators who seek rapid preparation for the RHCSA certification should instead start with RHCSA Rapid Track (RH199).This course is based on Red Hat Enterprise Linux 9.0.Course summaryInstall Red Hat Enterprise Linux using scalable methodsAccess security files, file systems, and networksExecute shell scripting and automation techniquesManage storage devices, logical volumes, and file systemsManage security and system accessControl the boot process and system servicesRun containersAudience for this courseThis course is geared toward Windows system administrators, network administrators, and other system administrators who are interested in supplementing current skills or backstopping other team members, in addition to Linux system administrators who are responsible for these tasks:Configuring, installing, upgrading, and maintaining Linux systems using established standards and proceduresProviding operational supportManaging systems for monitoring system performance and availabilityWriting and deploying scripts for task automation and system administrationRecommended trainingSuccessful completion of Red Hat System Administration I (RH124) is recommended.Experienced Linux administrators seeking to accelerate their path toward becoming a Red Hat Certified System Administrator should start with the RHCSA Rapid Track course (RH199).Take our free assessment to gauge whether this offering is the best fit for your skills.Technology considerationsThere are no special technology requirements.This course is not designed for bring your own device (BYOD).Internet access is not required, but is recommended to allow students to research and access Red Hat online resources.

Welcome to the Red Hat System Administration II (RH134) group in the Red Hat Learning Community!

Deanna

18 lip 2023

We are excited to launch a space dedicated to the Red Hat Training course Red Hat System Administration II! To gain the most value from this group - click the "Join Group" button in the upper right hand corner.We encourage group members to collaborate in this group to discuss topics, ask questions, share best practices and tips, provide course feedback, and share their accomplishments as it relates to RH134.Read more about Red Hat System Administration II here.

417

Revision: rh134-8.2-f0a9756