|
|
Line 62: |
Line 62: |
| We will now learn how to perform these operations (including monitoring of disk space usage) in Part 1. | | We will now learn how to perform these operations (including monitoring of disk space usage) in Part 1. |
| | | |
− | == Part 1: The /etc/passwd file == | + | == Part 1: Mounting and Un-mounting Partitions == |
| | | |
− | # Look at the <b><code><span style="color:#3366CC;font-size:1.2em;">/etc/passwd</span></code></b> file. | + | # x |
− | # Make note of the contents of that file.
| |
− | # Read about the file: http://man7.org/linux/man-pages/man5/passwd.5.html
| |
− | # Make sure you know what information each field contains.
| |
− | # Why do you think there are so many users?
| |
− | # Look at the names of the users. What do you think these user names represent? Are they people?
| |
− | # What is the numeric user ID (UID) of the root user?
| |
− | # The user IDs of real users (people) are different from the user IDs of system accounts. What is the pattern?
| |
| | | |
| '''Answer the Part 1 observations / questions in your lab log book.''' | | '''Answer the Part 1 observations / questions in your lab log book.''' |
| | | |
− | == Part 2: Adding users == | + | == Part 2: Obtaining File System Information == |
| | | |
| + | # x |
| | | |
− | #Perform this part in your '''centos1''' VM.
| + | '''Answer the Part 2 observations / questions in your lab log book.''' |
− | # Read the man page for the <b><code><span style="color:#3366CC;font-size:1.2em;">useradd</span></code></b> command.
| |
− | # Create three fictitious users (make-up their userids and full names. Give each of these newly-created users a password.
| |
− | # Grep the <b><code><span style="color:#3366CC;font-size:1.2em;">/etc/passwd</span></code></b> file for each of the new users.
| |
− | #* What is the '''home''' directory of each user?
| |
− | #* What '''group''' is each user in?
| |
− | #* What other information can you provide regarding these users?
| |
− | #* Where are the '''passwords''' stored?
| |
− | # Look at the man page for '''/etc/shadow''' using the command: <b><code><span style="color:#3366CC;font-size:1.2em;">man 5 shadow</span></code></b>
| |
− | #* Grep the <b><code><span style="color:#3366CC;font-size:1.2em;">/etc/shadow</span></code></b> file for each of the new users.
| |
− | #* Make note of this information.
| |
− | # Create two new dummy users, <b><code><span style="color:#3366CC;font-size:1.2em;">ops235_1</span></code></b> and <b><code><span style="color:#3366CC;font-size:1.2em;">ops235_2</span></code></b>.
| |
− | # Investigate the home directory of one of your new users.
| |
− | #* What files are there? Be sure to include hidden files.
| |
− | #* What do you think these files are used for?
| |
− | #* How does the operating system determine which files are created in a new home account? The answer can be found here:<br>http://www.linuxhowtos.org/Tips%20and%20Tricks/using_skel.htm
| |
− | #* Look at the files (including hidden files) in the template directory referred to in the article. Compare them to what is in a home directory for a new user. What do you notice?
| |
− | #* Create a new file in this directory with the following command: <b><code><span style="color:#3366CC;font-size:1.2em;">touch foo</span></code></b>
| |
− | #* Create a new user named <b><code><span style="color:#3366CC;font-size:1.2em;">foobar</span></code></b>, with the option to automatically create a home directory.
| |
− | #* Look at the contents of foobar's home directory. What do you notice?
| |
− | # Be sure to record your observations in your lab notes.
| |
− | #Issue the man pages for the '''useradd''' command. Explain the purpose of using the '''-e''' option for the ''useradd'' command. Try to think what would be the purpose for a Linux sysadmin to use this option when creating new users.
| |
| | | |
− | '''Answer the Part 2 observations / questions in your lab log book.'''
| |
| | | |
− | == Part 3: Managing Groups ==
| |
| | | |
− | #Remain in your '''centos1''' VM for this section.
| + | =INVESTIGATION 2: Adjusting File System Sizes with LVM= |
− | # Read the man page for the <b><code><span style="color:#3366CC;font-size:1.2em;">groupadd</span></code></b> and <b><code><span style="color:#3366CC;font-size:1.2em;">groupdel</span></code></b> commands.
| |
− | # Note which option allows you to set the Group ID number ('''GID''') when you create a new group.
| |
− | # Examine the file <b><code><span style="color:#3366CC;font-size:1.2em;">/etc/group</span></code></b>
| |
− | #* Which values of GID are reserved for system accounts?
| |
− | #* Which values of GID are reserved for non-system user accounts?
| |
− | #* What is the lowest available GID number for non-system users?
| |
− | #* What is the default group name of a new user?
| |
− | #* Add a new group named <b><code><span style="color:#3366CC;font-size:1.2em;">ops235</span></code></b> with a GID of <b><code><span style="color:#3366CC;font-size:1.2em;">600</span></code></b>.
| |
− | #* The management at your organization have concerns regarding some irresponsible users on your system.
| |
− | #** Add a new group named '''investigation'''.
| |
− | #** Look at '''/etc/group''' and note the GID of group called '''investigation'''.
| |
− | #** What GID is given to a new group if you do not specify it?
| |
− | #** In the file, add those users to the end of the concerned group (separate each user-name with a comma).
| |
− | #** Those individuals have explained their actions to management and the crisis has been resolved. Delete the '''investigation''' group.
| |
− | #** Look at '''/etc/group''' again and note the change.
| |
| | | |
− | '''Answer the Part 3 observations / questions in your lab log book.'''
| + | Monitoring and ensuring adequate space for a Linux file-system is considered to be an important task for a sys admin. |
| | | |
− | == Part 4: Deleting / Modifying Users == | + | === Part 1: Obtaining System Information with LVM === |
| | | |
− | #Remain in your '''centos1''' VM for this section.
| + | We have seen that maintaining unneeded '''packages can be a security risk''' due to the unnecessary increase in the complexity of your system. Similarly, it is also unnecessarily hazardous, and even more so, to leave unneeded services running. In this investigation, we will learn how to '''control services, and turn off those services that we think are not necessary to help reduce security risks'''.}} |
− | # Read the man page for the '''userdel''' command. Note which option automatically removes the users home directory when that user is deleted.
| |
− | # Delete the user '''ops235_1''' using the command <b><code><span style="color:#3366CC;font-size:1.2em;">userdel ops235_1</span></code></b>
| |
− | # Delete the user '''ops235'''_2 using the same command with the option which removes the home directory of the user.
| |
− | # Check the contents of the /home directory. What do you notice?
| |
− | # Check the contents of the <b><code><span style="color:#3366CC;font-size:1.2em;">/etc/group</span></code></b> file. What do you notice?
| |
− | # Read the man page for the usermod command. Note which options change the user's full name, primary group, supplementary groups, and shell.
| |
− | # Create a new user account called '''noobie''' for the employee: '''"Really Green"''' . Assign a password for that newly created user.
| |
− | # Management has indicated that this employee be on on probation for 3 months. Use the '''usermod''' command to set the account for noobie to expire in 3 months from this day as part of the security policy of this organization.
| |
− | # Add each of your new users to the group ops235 (in other words, add ops235 to each user as a supplementary group).
| |
− | # Examine <b><code><span style="color:#3366CC;font-size:1.2em;">/etc/group</span></code></b>. What has changed?
| |
− | # Use the '''usermod''' command to change the full name of the user account '''noobie''' from '''"Really Green"''' to '''"Outstanding Employee"'''. Examine the result of running that command in the <b><code><span style="color:#3366CC;font-size:1.2em;">/etc/passwd</span></code></b> file. What has changed?
| |
− | # Use the '''usermod''' command to extend the use of their account for 5 years as of today.
| |
− | # Be sure to record your observations in your lab notes.
| |
| | | |
− | '''Answer the Part 4 observations / questions in your lab log book.'''
| + | # x |
| | | |
− | =INVESTIGATION 2: Adjusting File System Sizes with LVM=
| + | '''Answer Part 1 observations / questions in your lab log book.''' |
| | | |
− | Monitoring and ensuring adequate space for a Linux file-system is considered to be an important task for a sys admin.
| |
| | | |
− | === Part 1: How do we Manage System Services? === | + | ===Part 2: Adjusting Partition Sizes with LVM=== |
| | | |
− | We have seen that maintaining unneeded '''packages can be a security risk''' due to the unnecessary increase in the complexity of your system. Similarly, it is also unnecessarily hazardous, and even more so, to leave unneeded services running. In this investigation, we will learn how to '''control services, and turn off those services that we think are not necessary to help reduce security risks'''.}}
| + | x |
| | | |
− | #Use your '''centos2''' VM for this part.
| |
− | <ol>
| |
− | <li value="2">Use the '''man''' pages to learn about the '''service''' command.</li><li>Issue the following Linux command:
| |
− | <ul>
| |
− | <li><b><code><span style="color:#3366CC;font-size:1.2em;">service --status-all</span></code></b></li>
| |
− | </ul>
| |
− | </li>
| |
− | <li>Note the services that are currently running.</li>
| |
− | <li>Use the command <b><code><span style="color:#3366CC;font-size:1.2em;">service iptables stop</span></code></b> to stop the service named '''iptables'''</li>
| |
− | <li>Run a command to verify that the '''iptables''' service has stopped.</li>
| |
− | <li>A newer method of managing services is by using '''systemd'''. It has the ability to manage dependent service in parallel and allow one service to be stopped without disrupting the other services. Here is a link that briefly explains how to use '''systemd''' (as opposed to tradition method: ''init'') and the '''systemctl''' command: [http://zenit.senecac.on.ca/wiki/index.php/Init_vs_systemd init vs systemd]</li>
| |
− | <li>If you reboot now - the iptables service will be turned back on. We don't want it on though, it causes students headaches. To turn it off permanently we need to use the '''chkconfig''' command:<br><b><code><span style="color:#3366CC;font-size:1.2em;">chkconfig iptables off</span></code></b></li>
| |
− | <li>Use the '''systemctl''' command (from the link above - showing examples) to verify that the '''iptables''' service is off ('''hint:''' issue command, and pipe to grep "'''iptables'''").
| |
− | <li>Reboot and confirm that it's no longer running.</li>
| |
− | </ol>
| |
| | | |
− | '''Answer Part 1 observations / questions in your lab log book.'''
| + | # x |
| | | |
| | | |
− | ===Part 2: How do we Manage Runlevels?===
| + | '''Answer Part 2 observations / questions in your lab log book.''' |
| | | |
− | Running servers in graphical mode will make your system most likely to be penetrated. The X-windows framework can be vulnerable to attacks when these servers are connected to the Internet. This is why when you install server versions of Linux, they work in text-based mode only. Desktop versions of Linux are then installed on workstations (working in graphical mode) that connect to the server (for security reasons).
| + | ===Part 3: Adding Virtual Hard Disks and Managing with LVM=== |
| | | |
− | The Linux sysadmin can also change the run-level (or state) of a graphical Linux server to run in text-based mode and run the graphical mode by issuing a command when graphic mode is required. The run-level term is now deprecated in Fedora, and will likely be deprecated in RHEL/CentOS at some point as well, but for now this is what the industry is using.
| + | x |
| | | |
| | | |
| + | # x |
| | | |
− | #Perform this part in both your '''centos2''' and '''centos3''' VMs.
| |
− | <ol>
| |
− | <li value="2">Issue the following Linux command:
| |
− | <ul>
| |
− | <li><b><code><span style="color:#3366CC;font-size:1.2em;">runlevel</span></code></b></li>
| |
− | </ul>
| |
− | </li>
| |
− | <li>Note the difference in output between '''centos2''' and '''centos3'''.</li>
| |
− | <li>You can use the '''init''' command to change the current run-level. See a list of runlevels [https://www.centos.org/docs/5/html/5.2/Installation_Guide/s2-init-boot-shutdown-rl.html here].</li><li> Use the '''man''' command to learn how to use the '''init''' command. Use this command to change the current run-level in '''centos2''' to '''3'''. What happened?</li>
| |
− | <li>Issue the following Linux command:
| |
− | <ul>
| |
− | <li><b><code><span style="color:#3366CC;font-size:1.2em;">startx</span></code></b></li>
| |
− | </ul>
| |
− | </li>
| |
− | <li>What happens?</li>
| |
− | <li>Log-off your graphical system. You should return to your shell prompt.</li>
| |
− | <li>Using systemd requires a different method of setting text mode and graphical mode. You can refer to this link for future reference:
| |
− | [http://fedoraproject.org/wiki/Systemd#How_do_I_change_the_runlevel.3F How to Change Run-Levels with Systemd]</li><li>Restart your centos2 machine, and make certain that it runs in '''graphical''' mode</li>
| |
− | </li>Why would you want to make a graphical Linux system run in text-based mode?</li>
| |
− | </ol>
| |
| | | |
| + | '''Answer Part 3 observations / questions in your lab log book.''' |
| | | |
− | '''Answer Part 2 observations / questions in your lab log book.'''
| |
| | | |
| | | |
| = INVESTIGATION 3: LOOKING AHEAD = | | = INVESTIGATION 3: LOOKING AHEAD = |
| | | |
− | ==Automating Routine Tasks (Shell Scripting)== | + | ==Automating Routine Tasks (Shell Scripting and Using Crontab)== |
| {|width="40%" align="right" cellpadding="10" | | {|width="40%" align="right" cellpadding="10" |
| |- valign="top" | | |- valign="top" |
LAB PREPARATION
Purpose / Objectives of Lab 5
The purpose of this lab is to discuss how a Linux sys admin can manage partitions including adjusting the size of their Linux systems if space is required. Various topics will be discussed including:
- Connecting and Disconnecting Directories to existing partitions (mount, umount).
- Monitoring Disk Space (df -h).
- Using LVM to resize partitions graphically and via commands.
- Create, partition and format virtual hard disks to increase the size of a file system.
- Create a Bash Shell Script to monitor and report low disk size (run periodically in crontab).
Minimum Required Materials
Removable Hard Disk Pack (SATA)
|
|
|
My Toolkit (CLI Reference)
LVM Information:
|
LVM Management
|
Miscellaneous
|
INVESTIGATION 1: File System Management
We take for granted that a file-system must be mounted (for example the root partition) in order for a Linux system to be usable upon system start-up. The /etc/fstab (file system table) contains entries to mount various file systems automatically upon start-up of the Linux system.
The Linux sys admin also has the ability to manually mount (connect) and un-mount (disconnect) partitions in order to perform maintenance on the file system (for example un-mounting the /home partition to install software and prevent users from logging in during that process).
We will now learn how to perform these operations (including monitoring of disk space usage) in Part 1.
Part 1: Mounting and Un-mounting Partitions
- x
Answer the Part 1 observations / questions in your lab log book.
Part 2: Obtaining File System Information
- x
Answer the Part 2 observations / questions in your lab log book.
INVESTIGATION 2: Adjusting File System Sizes with LVM
Monitoring and ensuring adequate space for a Linux file-system is considered to be an important task for a sys admin.
Part 1: Obtaining System Information with LVM
We have seen that maintaining unneeded packages can be a security risk due to the unnecessary increase in the complexity of your system. Similarly, it is also unnecessarily hazardous, and even more so, to leave unneeded services running. In this investigation, we will learn how to control services, and turn off those services that we think are not necessary to help reduce security risks.}}
- x
Answer Part 1 observations / questions in your lab log book.
Part 2: Adjusting Partition Sizes with LVM
x
- x
Answer Part 2 observations / questions in your lab log book.
Part 3: Adding Virtual Hard Disks and Managing with LVM
x
- x
Answer Part 3 observations / questions in your lab log book.
INVESTIGATION 3: LOOKING AHEAD
Automating Routine Tasks (Shell Scripting and Using Crontab)
Bash Shell Scripting Tips:- The case statement:
The case statement is a control-flow statement that works in a similar way as the if-elif-else statement (but is more concise). This statement presents scenerios or "cases" based on values or regular expressions (not ranges of values like if-elif-else statements). After action(s) are taken for a particular scenerio (or "case"), a break statement (;;) is used to "break-out" of the statement (and not perform other actions). A default case (*) is also used to catch exceptions.
Examples (try in shell script):
read -p "pick a door (1 or 2): " pick case $pick in 1) echo "You win a car!" ;; 2) echo "You win a bag of dirt!" ;; *) echo "Not a valid entry" exit 1 ;; esac
read -p "enter a single digit: " digit case $digit in [0-9]) echo "Your single digit is: $digit" ;; *) echo "not a valid single digit" exit 1 ;; esac
- The getopts function:
The getopts function allows the shell scripter to create scripts that accept options (like options for Linux commands). This provides the Linux administrator with scripts that provide more flexibility and versatility. A built-in function called getopts (i.e. get command options) is used in conjunction with a while loop and a case statement to carry out actions based on if certain options are present when the shell script is run. The variable $OPTARG can be used if an option accepts text (denoted in the getopts function with an option letter followed by a colon. Case statement exceptions use the :) and \?) cases for error handling. Example of getopts (try in script and run with options) while getopts abc: name do case $name in a) echo "Action for option \"a\"" ;; b) echo "Action for option \"b\"" ;; c) echo "Action for option \"c\"" echo Value is: $OPTARG" ;; :) echo "Error: You need text after -c option" exit 1 ;; \?) echo "Error: Incorrect option" exit 1 ;; esac
|
We will now use shell scripting to help automate the task for a Linux adminstrator to create regular user accounts.
- Download, study, and run the following shell script. Issue the command:
wget https://scs.senecac.on.ca/~murray.saul/user-create.bash
- Try to understand what these Bash Shell scripts do, and then run the script as root. After running the shell script, view the contents of the /home directory to confirm.
Although the zenity command is a "user-friendly" way to run shell scripts, Linux administrators usually create shell scripts that resemble common Linux commands. In this lab, you will learn to create a shell script using the getopts function to make your shell script behave more like actual Linux commands (including the use of options). Refer to the notes section on the right-hand-side for reference about the case statement and the getopts function.
- Open a Bash shell terminal and login as root.
- Use the wget command to download the input file called user-data.txt by issuing the command:
wget https://scs.senecac.on.ca/~murray.saul/user-data.txt
- View the contents on the user-data.txt file to confirm there are 3 fields (username, fullname, and e-mail address)which are separated by the colon (:) symbol.
- Use a text editor (such as
vi
or nano
) to create a Bash Shell script called: createUsers.bash
in /root's home directory. - Enter the following text content into your text-editing session:
#!/bin/bash
# createUsers.bash
# Purpose: Generates a batch of user accounts (user data stored in a text file)
#
# USAGE:
#
# /root/createUsers.bash [-i {input-path}]
#
# Author: *** INSERT YOUR NAME ***
# Date: *** CURRENT DATE ***
if [ $PWD != "/root" ] # only runs if in root's home directory
then
echo "You must be in root's home directory." >&2
exit 1
fi
if [ "$#" -eq 0 ] # if no arguments after command
then
echo "You must enter an argument" >&2
echo "USAGE: $0 [-i {input-path}]" >&2
exit 2
fi
- Save your editing session, but remain in the text editor.
- The code displayed below uses the getopt function set the input file pathname or check for invalid options or missing option text. Add the following code
outputFlag="n"
while getopts i: name
do
case $name in
i) inputFile=$OPTARG ;;
:) echo "Error: You need text after options requiring text"
exit 1 ;;
\?) echo "Error: Incorrect option"
exit 1 ;;
esac
done
- Save your editing session, but remain in the text editor.
- The code displayed below uses logic to exit the script if the input file does not exist. Command substitution is used to store each line of the input file as a positional parameter. There is one subtle problem here: The full names of the users contain spaces which can create havoc when trying to set each line as a separate positional parameter. In this case the sed command is used to convert spaces to plus signs (+), which will be converted back later. Finally, a for loop is used to create each account (useradd) and mail the user their account information (mail). Add the following code:
if [ ! -f $inputFile ]
then
echo "The file pathname \"$inputFile\" is empty or does not exist" >&2
exit 2
fi
set $(sed 's/ /+/g' $inputFile) # temporarily convert spaces to + for storing lines as positional parameters
for x
do
useradd -m -c "$(echo $x | cut -d":" -f2 | sed 's/+/ /g')" -p $(date | md5sum | cut -d" " -f1) $(echo $x | cut -d":" -f1)
mail -s "Server Account Information" $(echo $x | cut -d":" -f3) <<+
Here is your server account information:
servername: myserver.senecac.on.ca
username: $(echo $x | cut -d":" -f1)
password: $(date | md5sum | cut -d" " -f1)
Regards,
IT Department
+
done
echo -e "\n\nAccounts have been created\n\n"
exit 0
- Save, set permissions, and then run that shell script for the input text file user-data.txt. Did it work? Try running the script without an argument - What did it do?
- You have completed lab4. Proceed to Completing The Lab, and follow the instructions for "lab sign-off".
Answer Investigation 3 observations / questions in your lab log book.
LAB 4 SIGN-OFF (SHOW INSTRUCTOR)
Time for a new backup!
If you have successfully completed this lab, make a new backup of your virtual machines. Remember to also make a backup of the new second virtual disk drive on centos1 -- you now have two virtual disks on centos1, and therefore two image files, and therefore will need two backup files.
Arrange proof of the following on the screen:
- ✓ Account created on centos1 VM.
- ✓ List contents of /etc/group file (ops235 group) on centos1 VM.
- ✓ List contents of /etc/passwd file (created accounts) on centos1 VM.
- ✓ Display current run-level status on centos2 VM.
- ✓ Creation of your bash shell script called createUsers.bash
Preparing for the Quizzes
- Describe all of the field in
/etc/passwd
- What is the command to create a user? What option to create a home directory for that user?
- What is the command to change the full name of an already-created user?
- What is the command to delete a user account? What option allows for the user's home directory to be removed as well?
- What is the command to create a group? What is the command (or steps) to include a user in a newly-created group?
- What is the purpose of
/etc/shadow
?
- What is the purpose of
/etc/skel
?
- What does the term run-level mean?
- How to set the run-level of a Linux system to text-based only? How to set to graphical mode?
- What is the command to view the status of running services?
- What is the command to start a service (like httpd, or sshd)?
- What is the command to start a service?
- Can a service be stopped and started by issuing just one command?