102-500 Exam Dumps : LPIC-1 Exam 102, Part 2 of 2, version 5.0

The command that allows you to make a shell variable visible to subshells is export VARIABLE. This command turns the variable into a global or environment variable, which means it can be accessed by any child process or subshell that inherits the environment of the parent shell. The syntax of the export command does not require a dollar sign ($) before the variable name, unlike when referencing the value of the variable. The other commands are either invalid or do not affect the visibility of the variable to subshells. The set command can be used to assign values to variables, but it does not export them. The env command can be used to run a command in a modified environment, but it does not change the environment of the current shell. References:

[LPI Linux Essentials - Topic 105: Shells, Scripting and Data Management]

[LPI Linux Professional - Exam 102 Objectives - Topic 105: Shells and Shell Scripting]

What is a Subshell? - Linux Bash Shell Scripting Tutorial Wiki - nixCraft

What is Subshell in Linux? [Explained]

The configuration file that contains the default options for SSH clients is /etc/ssh/ssh_config. This file is read by the ssh program when it connects to a remote SSH server. It can contain global options that apply to all hosts, or host-specific options that only apply to certain hosts or patterns. The /etc/ssh/ssh_config file is the system-wide default SSH client configuration file. It can be overridden by a user-specific configuration file ~/.ssh/config, which is located in the user’s home directory. The /etc/ssh/ssh_config file is part of the topic 110.1: Perform security administration tasks, 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 /etc/cron.allow file is a file that contains a list of users who are allowed to use the cron scheduling system. The cron scheduling system is a way of running commands or scripts at specified times or intervals. Users can create their own cron jobs by using the crontab command, which edits a file called crontab that stores the user’s scheduled tasks. However, not all users may have access to the crontab command or the cron system. The access is controlled by two files: /etc/cron.allow and /etc/cron.deny. If the /etc/cron.allow file exists, then only the users listed in this file can use the crontab command and the cron system. The file should have one user name per line. If the /etc/cron.allow file does not exist, then the /etc/cron.deny file is checked. If this file exists, then the users listed in this file are denied access to the crontab command and the cron system. If neither file exists, then the access depends on the configuration of the cron daemon, which is the program that runs the cron jobs. By default, only the root user can use the cron system if no files exist. The root user can always use the cron system regardless of the existence or content of these files. To create or edit the /etc/cron.allow file, the root user needs to use a text editor such as vi, nano, or emacs. For example, to allow the users alice and bob to use the cron system, the root user can use the following command:

sudo vi /etc/cron.allow

And then add the following lines to the file:

alice bob

And then save and exit the file. References:

How cron.allow and cron.deny can be used to limit access to crontab for …

/etc/cron.allow - Linux Bash Shell Scripting Tutorial Wiki

Linux / UNIX Restrict at / cron Usage To Authorized Users