https://wiki.ihitc.net/mediawiki/api.php?action=feedcontributions&feedformat=atom&user=Powe0122 2026-04-30T16:37:37Z User contributions MediaWiki 1.38.5 https://wiki.ihitc.net/mediawiki/index.php?title=Chapter_14_Study_Guide&diff=5704 2012-04-25T03:47:34Z

<p>Powe0122: </p> <hr /> <div>===TROUBLESHOOTING, PERFORMANCE, SECURITY===<br /> <br /> ===Troubleshooting Methodology===<br /> *Proactive Maintenance<br /> Taking the necessary steps to minimize future problems<br /> Includes performing system back-ups and identifying potential problem areas.<br /> *Reactive Maintenance<br /> Correcting problems when they arise<br /> Always document the solution to help quickly resolve future problems<br /> <br /> ===Troubleshooting Procedures===<br /> *Gather as much information as possible<br /> System log files<br /> Run information utilities such as ps or mount<br /> “tail –f /path/to/logfile” opens a log file for continuous viewing<br /> *Isolate the problem<br /> Determine if the problem is persistent, intermittent, and how many users are effected<br /> *List possible causes and solutions<br /> google is your best friend<br /> *Implement and test solution<br /> *Document your solution and process<br /> <br /> *Prioritize problems<br /> Solve most severe problems first<br /> Spending too much time on small problems can result in reduced productivity<br /> *Try to solve the root of the problem<br /> A short term solution might fail in the long term because of an underlying problem<br /> <br /> ===Hardware Related Problems===<br /> *Can come from damaged hardware or improper hardware or software configuration<br /> *Using the dmesg command or viewing the /var/log/boot.log and var/log/messages files can isolate most hardware problems<br /> *The absence of or improper drivers prevents the OS from using the associated hardware<br /> Use lsusb to view only usb devices<br /> Use lspci to view only PCI devices<br /> *Lsmod command lists the drivers loaded into the kernel<br /> By comparing the output of dmesg, lsusb, and lspci with the lsmod output, you can determine if a driver is missing<br /> *Hard drives are the most common hardware component to fail<br /> <br /> ===software Related Problems===<br /> *Can be application or OS related<br /> *Application Related Problems<br /> Can fail during execution due to missing program libraries and files, process restrictions, or conflicting applications<br /> Identify missing files in a package by using the –V option with the rpm command<br /> Use the ldd command to identify which shared libraries are required by certain programs<br /> It is good practice to run the ldconfig command to ensure the shared library directories are updated<br /> The ulimit command can be used to increase the number of processes the user can start in a shell<br /> <br /> ===Operating System Related Problems===<br /> Typically include problems with X windows, boot loaders, and filesystems<br /> Use xwininfo or xdpyinfo commands to attemp to isolate problems with X windows<br /> Placing the word “linear” and removing “compact” from the /etc/lilo.conf file often fixes LILO boot loader problems<br /> The GRUB boot loader errors are typically the result of a missing file in the /boot directory<br /> File systems can become corrupted due to high use accessing the hard drive<br /> Corrupted filesystems can be identified by very slow write requests, errors printed to the console, or failure to mount<br /> <br /> ===User Interface Related Problems===<br /> *Users need to understand how to use their desktop environment, but often will not<br /> *Assistive technologies are tools you can use to modify your desktop experience<br /> Accessed by opening the system menu and navigate to preferences, assistive technologies<br /> <br /> <br /> ===Linux Performance===<br /> <br /> Monitor system performance using command-line included in the sysstat package.<br /> To make it easier to identify performance problems, a network administrator should run performance utilities on healthy Linux systems to develop a baseline.<br /> <br /> '''Performance Problems:'''<br /> *Software<br /> *Hardware<br /> *Combination of the two<br /> <br /> '''Software Problems'''<br /> <br /> Software that requires too many system resources may use CPU, memory, and peripheral devices creating poor performance.<br /> Too many processes running or rouge processes<br /> <br /> '''Hardware Problems'''<br /> <br /> Improperly configured hardware (May still Work)<br /> Old ( Most companies retire computer equipment after two to five years of use)<br /> Jabbering: Sending large amounts of information to the CPU when not in use.<br /> <br /> '''Resolutions'''<br /> <br /> Software problems can sometimes be resolved by changing hardware.<br /> Move or Remove the software<br /> Upgrading or adding another CPU<br /> Use bus mastering peripheral components (Devices that can perform processes normally performed by the CPU)<br /> Adding RAM to increase system speed<br /> Replace slower disk drives with faster ones<br /> Use disk striping RAID<br /> Keep CD and DVD drives on a separate hard disk controller<br /> <br /> ===Monitoring Performance with sysstat Utilities===<br /> <br /> Using information from the /proc directory and system devices, the System Statistics (sysstat) package contains utilities that monitor the system.<br /> To install the latest version of sysstat on a Linux system, use the following method:<br /> 1. yum install sysstat <br /> <br /> '''Three of the System Statistics (sysstat) package performance monitoring utilities include:'''<br /> *mpstat (multiple processor statistics) command<br /> *iostat (input/output statistics)<br /> *sar (system activity reported) command<br /> <br /> '''mpstat (multiple processor statistics)'''<br /> <br /> Used to monitor CPU performance for all processors on the system since the system was started or rebooted.<br /> <br /> ''To monitor a single cpu use the –P option followed by the processor number.'' <br /> <br /> Example: mpstat –P 0 would display the first processor on the system.<br /> Limited in abilities<br /> <br /> <br /> '''Examining the Output of the mpstat command'''<br /> <br /> *%user= % of time the processor spent executing user programs and daemons<br /> *%nice= % of time the processor spent executing programs and daemons that had nondefault nice values <br /> *%sys= % of time the processor spent maintaining itself<br /> *%iowait= % of time the CPU was idle when an outstanding disk I/O request existed.<br /> *%irq= % of time the CPU is using to respond to normal interrupts that span multiple CPUs. <br /> *%soft= % of time the CPU is using to respond to normal interrupts that span multiple CPUs<br /> *%steal= % of time the CPU is waiting to respond to virtual CPU requests <br /> *%guest= % of time the CPU is executing another virtual CPU<br /> *%idle= % of time the CPU did not spend executing tasks. Should be greater than 25% over a long period of time. <br /> <br /> '''iostat (input/output statistics)'''<br /> <br /> Measusres the flow of information to and from disk devices.<br /> Displays CPU statistics similar to mpstat<br /> Limited in abilities<br /> Adds transfers per second (tps) and block <br /> <br /> '''sar (system activity reporter)'''<br /> <br /> Displays more information than the mpstat or iostat command<br /> Displays CPU statistics by default<br /> Most widely used performance monitoring tool on UNIX and Linux systems<br /> Scheduled using the cron daemon to run every 10 minutes for the current day<br /> logged to a file in the /var/log/sa directory called sa#. The # represents the day of the month<br /> Only one month of records is kept but can be changed by editing the cron table located at /etc/cron.d/sysstat<br /> Can display different statistics by specifying options<br /> sar (system activity reporter)<br /> Displays more information than the mpstat or iostat command<br /> Displays CPU statistics by default<br /> Most widely used performance monitoring tool on UNIX and Linux systems<br /> Scheduled using the cron daemon to run every 10 minutes for the current day<br /> logged to a file in the /var/log/sa directory called sa#. The # represents the day of the month<br /> Only one month of records is kept but can be changed by editing the cron table located at /etc/cron.d/sysstat<br /> Can display different statistics by specifying options<br /> <br /> '''Common options with the sar caommand'''<br /> <br /> *CPU Usage of ALL CPUs (sar -u) Default<br /> *CPU Usage of Individual CPU or Core (sar -P)<br /> *Memory Free and Used (sar -r)<br /> *Display swapping statistics (sar -W)<br /> *Reports run queue and load average (sar -q)<br /> *sar -u 1 3 Displays real time CPU usage every 1 second for 3 times.<br /> <br /> ===Other Performance Monitoring Utilities===<br /> <br /> *top utility (discussed in Chapter 9)<br /> *free command can be used to display the total amounts of physical and swap memory (in Kilobytes) and their utilizations.<br /> *vmstat command indicates more information than the free command to indicate whether more physical memory is required.<br /> <br /> <br /> ===Security===<br /> '''Locking enviorment'''<br /> <br /> Local Computer<br /> In GUI environment always lock screen when away from system<br /> In CMD enviorment, not as easy as exiting will end process, instead of exiting use nohup command to exit shell without terminating processes. <br /> <br /> <br /> '''Root time minimization'''<br /> The root user should only be used in conditions where it is specically called for, this is done to limit the exposure to potential threats both internally and externally.<br /> Use the su command to elevate your permissions when needed<br /> <br /> '''Root time minimization'''<br /> If only a single command is going to be run as root you can use the –c variable to modify to return to user after command is executed. <br /> <br /> <br /> '''Network Protection'''<br /> The biggest part of protecting your system from network intrusion is to terminated unneeded services. Using a program like nmap will display what ports are currently open and available. <br /> These are stored in etc/services, ensure they are disabled in the runlevel when not needed. <br /> For Internet Super Daemon, need to add the disable = yes to the appropriate service. <br /> <br /> <br /> '''Network Intrusion'''<br /> Prevention of the login using common users should have the shell listed in the /etc/passwd tied to /sbin/nologin. <br /> This will prevent attackers from logging into the system using these shells. It will display your preprogrammed message /etc/nologin.txt, if none exists a standard one will be displayed. <br /> <br /> <br /> '''Don’t be a fool wrap your tool!'''<br /> TCP wrappers should be used as a tool to secure services started by the Internet Super Daemon. <br /> To use the wrapper modify /etc/zinetd.d and start the network daemon.<br /> <br /> <br /> '''Host Allow vs. Deny'''<br /> When using the wrapper it will check against your Allow and Deny lists to ensure host connection<br /> <br /> <br /> '''FIREWALL!!'''<br /> Arguably the most important part of a network environment is your firewall, be it operated in a hardware device or software. <br /> This is done using the netfiler/iptables<br /> Rules… rules… rules… <br /> INPUT: Coming into system<br /> FORWARD: Pass through system<br /> OUTPUT: Leaving from system with origination<br /> <br /> <br /> '''Firewall setup'''<br /> Using the iptables command each of the arguments can be entered to determine network traffic. <br /> <br /> <br /> '''SELinux'''<br /> Security Enhanced Linux, in newer versions in configured by default. <br /> Patches and utilities created by the NSA that is role based security. <br /> To enable SELinux edit /etc/selinux/config<br /> SELINUX = enforcing<br /> SELINUX = permissive<br /> SELINUX = disabled<br /> <br /> <br /> '''Encryption'''<br /> Two most common on linux are SSH and GPG (GNU Privacy Guard)<br /> RSA to encrypt data<br /> DSA to sign data<br /> Keys are stored in;<br /> ssh_host_dsa_key(.pub)<br /> ssh_host_rsa_key(.pub)<br /> (.pub) on end is the public key<br /> <br /> <br /> '''Intrusion Detection''''<br /> When running services regularly check log files in /var/log for associated services<br /> PAM (pluggable Authentication Modules), logs information into /var/log/secure for errors and alerts<br /> Open files can be vied using lsof (list of open files)</div>

Powe0122 https://wiki.ihitc.net/mediawiki/index.php?title=Chapter_14_Study_Guide&diff=5703 2012-04-25T03:41:18Z

<p>Powe0122: </p> <hr /> <div>'''TROUBLESHOOTING, PERFORMANCE, SECURITY'''<br /> <br /> '''Troubleshooting Methodology'''<br /> *Proactive Maintenance<br /> Taking the necessary steps to minimize future problems<br /> Includes performing system back-ups and identifying potential problem areas.<br /> *Reactive Maintenance<br /> Correcting problems when they arise<br /> Always document the solution to help quickly resolve future problems<br /> <br /> '''Troubleshooting Procedures'''<br /> *Gather as much information as possible<br /> System log files<br /> Run information utilities such as ps or mount<br /> “tail –f /path/to/logfile” opens a log file for continuous viewing<br /> *Isolate the problem<br /> Determine if the problem is persistent, intermittent, and how many users are effected<br /> *List possible causes and solutions<br /> google is your best friend<br /> *Implement and test solution<br /> *Document your solution and process<br /> <br /> *Prioritize problems<br /> Solve most severe problems first<br /> Spending too much time on small problems can result in reduced productivity<br /> *Try to solve the root of the problem<br /> A short term solution might fail in the long term because of an underlying problem<br /> <br /> '''Hardware Related Problems'''<br /> *Can come from damaged hardware or improper hardware or software configuration<br /> *Using the dmesg command or viewing the /var/log/boot.log and var/log/messages files can isolate most hardware problems<br /> *The absence of or improper drivers prevents the OS from using the associated hardware<br /> Use lsusb to view only usb devices<br /> Use lspci to view only PCI devices<br /> *Lsmod command lists the drivers loaded into the kernel<br /> By comparing the output of dmesg, lsusb, and lspci with the lsmod output, you can determine if a driver is missing<br /> *Hard drives are the most common hardware component to fail<br /> <br /> '''Software Related Problems'''<br /> *Can be application or OS related<br /> *Application Related Problems<br /> Can fail during execution due to missing program libraries and files, process restrictions, or conflicting applications<br /> Identify missing files in a package by using the –V option with the rpm command<br /> Use the ldd command to identify which shared libraries are required by certain programs<br /> It is good practice to run the ldconfig command to ensure the shared library directories are updated<br /> The ulimit command can be used to increase the number of processes the user can start in a shell<br /> <br /> *Operating System Related Problems<br /> Typically include problems with X windows, boot loaders, and filesystems<br /> Use xwininfo or xdpyinfo commands to attemp to isolate problems with X windows<br /> Placing the word “linear” and removing “compact” from the /etc/lilo.conf file often fixes LILO boot loader problems<br /> The GRUB boot loader errors are typically the result of a missing file in the /boot directory<br /> File systems can become corrupted due to high use accessing the hard drive<br /> Corrupted filesystems can be identified by very slow write requests, errors printed to the console, or failure to mount<br /> <br /> '''User Interface Related Problems'''<br /> *Users need to understand how to use their desktop environment, but often will not<br /> *Assistive technologies are tools you can use to modify your desktop experience<br /> Accessed by opening the system menu and navigate to preferences, assistive technologies<br /> <br /> <br /> '''Linux Performance'''<br /> <br /> Monitor system performance using command-line included in the sysstat package.<br /> To make it easier to identify performance problems, a network administrator should run performance utilities on healthy Linux systems to develop a baseline.<br /> <br /> '''Performance Problems:'''<br /> *Software<br /> *Hardware<br /> *Combination of the two<br /> <br /> '''Software Problems'''<br /> <br /> Software that requires too many system resources may use CPU, memory, and peripheral devices creating poor performance.<br /> Too many processes running or rouge processes<br /> <br /> '''Hardware Problems'''<br /> <br /> Improperly configured hardware (May still Work)<br /> Old ( Most companies retire computer equipment after two to five years of use)<br /> Jabbering: Sending large amounts of information to the CPU when not in use.<br /> <br /> '''Resolutions'''<br /> <br /> Software problems can sometimes be resolved by changing hardware.<br /> Move or Remove the software<br /> Upgrading or adding another CPU<br /> Use bus mastering peripheral components (Devices that can perform processes normally performed by the CPU)<br /> Adding RAM to increase system speed<br /> Replace slower disk drives with faster ones<br /> Use disk striping RAID<br /> Keep CD and DVD drives on a separate hard disk controller<br /> <br /> '''Monitoring Performance with sysstat Utilities'''<br /> <br /> Using information from the /proc directory and system devices, the System Statistics (sysstat) package contains utilities that monitor the system.<br /> To install the latest version of sysstat on a Linux system, use the following method:<br /> 1. yum install sysstat <br /> <br /> '''Three of the System Statistics (sysstat) package performance monitoring utilities include:'''<br /> *mpstat (multiple processor statistics) command<br /> *iostat (input/output statistics)<br /> *sar (system activity reported) command<br /> <br /> '''mpstat (multiple processor statistics)'''<br /> <br /> Used to monitor CPU performance for all processors on the system since the system was started or rebooted.<br /> <br /> ''To monitor a single cpu use the –P option followed by the processor number.'' <br /> <br /> Example: mpstat –P 0 would display the first processor on the system.<br /> Limited in abilities<br /> <br /> <br /> '''Examining the Output of the mpstat command'''<br /> <br /> *%user= % of time the processor spent executing user programs and daemons<br /> *%nice= % of time the processor spent executing programs and daemons that had nondefault nice values <br /> *%sys= % of time the processor spent maintaining itself<br /> *%iowait= % of time the CPU was idle when an outstanding disk I/O request existed.<br /> *%irq= % of time the CPU is using to respond to normal interrupts that span multiple CPUs. <br /> *%soft= % of time the CPU is using to respond to normal interrupts that span multiple CPUs<br /> *%steal= % of time the CPU is waiting to respond to virtual CPU requests <br /> *%guest= % of time the CPU is executing another virtual CPU<br /> *%idle= % of time the CPU did not spend executing tasks. Should be greater than 25% over a long period of time. <br /> <br /> '''iostat (input/output statistics)'''<br /> <br /> Measusres the flow of information to and from disk devices.<br /> Displays CPU statistics similar to mpstat<br /> Limited in abilities<br /> Adds transfers per second (tps) and block <br /> <br /> '''sar (system activity reporter)'''<br /> <br /> Displays more information than the mpstat or iostat command<br /> Displays CPU statistics by default<br /> Most widely used performance monitoring tool on UNIX and Linux systems<br /> Scheduled using the cron daemon to run every 10 minutes for the current day<br /> logged to a file in the /var/log/sa directory called sa#. The # represents the day of the month<br /> Only one month of records is kept but can be changed by editing the cron table located at /etc/cron.d/sysstat<br /> Can display different statistics by specifying options<br /> sar (system activity reporter)<br /> Displays more information than the mpstat or iostat command<br /> Displays CPU statistics by default<br /> Most widely used performance monitoring tool on UNIX and Linux systems<br /> Scheduled using the cron daemon to run every 10 minutes for the current day<br /> logged to a file in the /var/log/sa directory called sa#. The # represents the day of the month<br /> Only one month of records is kept but can be changed by editing the cron table located at /etc/cron.d/sysstat<br /> Can display different statistics by specifying options<br /> <br /> '''Common options with the sar caommand'''<br /> <br /> *CPU Usage of ALL CPUs (sar -u) Default<br /> *CPU Usage of Individual CPU or Core (sar -P)<br /> *Memory Free and Used (sar -r)<br /> *Display swapping statistics (sar -W)<br /> *Reports run queue and load average (sar -q)<br /> *sar -u 1 3 Displays real time CPU usage every 1 second for 3 times.<br /> <br /> '''Other Performance Monitoring Utilities'''<br /> <br /> *top utility (discussed in Chapter 9)<br /> *free command can be used to display the total amounts of physical and swap memory (in Kilobytes) and their utilizations.<br /> *vmstat command indicates more information than the free command to indicate whether more physical memory is required.<br /> <br /> <br /> '''Security'''<br /> '''Locking enviorment'''<br /> <br /> Local Computer<br /> In GUI environment always lock screen when away from system<br /> In CMD enviorment, not as easy as exiting will end process, instead of exiting use nohup command to exit shell without terminating processes. <br /> <br /> <br /> '''Root time minimization'''<br /> The root user should only be used in conditions where it is specically called for, this is done to limit the exposure to potential threats both internally and externally.<br /> Use the su command to elevate your permissions when needed<br /> <br /> '''Root time minimization'''<br /> If only a single command is going to be run as root you can use the –c variable to modify to return to user after command is executed. <br /> <br /> <br /> '''Network Protection'''<br /> The biggest part of protecting your system from network intrusion is to terminated unneeded services. Using a program like nmap will display what ports are currently open and available. <br /> These are stored in etc/services, ensure they are disabled in the runlevel when not needed. <br /> For Internet Super Daemon, need to add the disable = yes to the appropriate service. <br /> <br /> <br /> '''Network Intrusion'''<br /> Prevention of the login using common users should have the shell listed in the /etc/passwd tied to /sbin/nologin. <br /> This will prevent attackers from logging into the system using these shells. It will display your preprogrammed message /etc/nologin.txt, if none exists a standard one will be displayed. <br /> <br /> <br /> '''Don’t be a fool wrap your tool!'''<br /> TCP wrappers should be used as a tool to secure services started by the Internet Super Daemon. <br /> To use the wrapper modify /etc/zinetd.d and start the network daemon.<br /> <br /> <br /> '''Host Allow vs. Deny'''<br /> When using the wrapper it will check against your Allow and Deny lists to ensure host connection<br /> <br /> <br /> '''FIREWALL!!'''<br /> Arguably the most important part of a network environment is your firewall, be it operated in a hardware device or software. <br /> This is done using the netfiler/iptables<br /> Rules… rules… rules… <br /> INPUT: Coming into system<br /> FORWARD: Pass through system<br /> OUTPUT: Leaving from system with origination<br /> <br /> <br /> '''Firewall setup'''<br /> Using the iptables command each of the arguments can be entered to determine network traffic. <br /> <br /> <br /> '''SELinux'''<br /> Security Enhanced Linux, in newer versions in configured by default. <br /> Patches and utilities created by the NSA that is role based security. <br /> To enable SELinux edit /etc/selinux/config<br /> SELINUX = enforcing<br /> SELINUX = permissive<br /> SELINUX = disabled<br /> <br /> <br /> '''Encryption'''<br /> Two most common on linux are SSH and GPG (GNU Privacy Guard)<br /> RSA to encrypt data<br /> DSA to sign data<br /> Keys are stored in;<br /> ssh_host_dsa_key(.pub)<br /> ssh_host_rsa_key(.pub)<br /> (.pub) on end is the public key<br /> <br /> <br /> '''Intrusion Detection''''<br /> When running services regularly check log files in /var/log for associated services<br /> PAM (pluggable Authentication Modules), logs information into /var/log/secure for errors and alerts<br /> Open files can be vied using lsof (list of open files)</div>

Powe0122 https://wiki.ihitc.net/mediawiki/index.php?title=Chapter_14_Study_Guide&diff=5702 2012-04-25T03:32:57Z

<p>Powe0122: </p> <hr /> <div>'''Troubleshooting Methodology'''<br /> *Proactive Maintenance<br /> Taking the necessary steps to minimize future problems<br /> Includes performing system back-ups and identifying potential problem areas.<br /> *Reactive Maintenance<br /> Correcting problems when they arise<br /> Always document the solution to help quickly resolve future problems<br /> <br /> '''Troubleshooting Procedures'''<br /> *Gather as much information as possible<br /> System log files<br /> Run information utilities such as ps or mount<br /> “tail –f /path/to/logfile” opens a log file for continuous viewing<br /> *Isolate the problem<br /> Determine if the problem is persistent, intermittent, and how many users are effected<br /> *List possible causes and solutions<br /> google is your best friend<br /> *Implement and test solution<br /> *Document your solution and process<br /> <br /> *Prioritize problems<br /> Solve most severe problems first<br /> Spending too much time on small problems can result in reduced productivity<br /> *Try to solve the root of the problem<br /> A short term solution might fail in the long term because of an underlying problem<br /> <br /> '''Hardware Related Problems'''<br /> *Can come from damaged hardware or improper hardware or software configuration<br /> *Using the dmesg command or viewing the /var/log/boot.log and var/log/messages files can isolate most hardware problems<br /> *The absence of or improper drivers prevents the OS from using the associated hardware<br /> Use lsusb to view only usb devices<br /> Use lspci to view only PCI devices<br /> *Lsmod command lists the drivers loaded into the kernel<br /> By comparing the output of dmesg, lsusb, and lspci with the lsmod output, you can determine if a driver is missing<br /> *Hard drives are the most common hardware component to fail<br /> <br /> '''Software Related Problems'''<br /> *Can be application or OS related<br /> *Application Related Problems<br /> Can fail during execution due to missing program libraries and files, process restrictions, or conflicting applications<br /> Identify missing files in a package by using the –V option with the rpm command<br /> Use the ldd command to identify which shared libraries are required by certain programs<br /> It is good practice to run the ldconfig command to ensure the shared library directories are updated<br /> The ulimit command can be used to increase the number of processes the user can start in a shell<br /> <br /> *Operating System Related Problems<br /> Typically include problems with X windows, boot loaders, and filesystems<br /> Use xwininfo or xdpyinfo commands to attemp to isolate problems with X windows<br /> Placing the word “linear” and removing “compact” from the /etc/lilo.conf file often fixes LILO boot loader problems<br /> The GRUB boot loader errors are typically the result of a missing file in the /boot directory<br /> File systems can become corrupted due to high use accessing the hard drive<br /> Corrupted filesystems can be identified by very slow write requests, errors printed to the console, or failure to mount<br /> <br /> '''User Interface Related Problems'''<br /> *Users need to understand how to use their desktop environment, but often will not<br /> *Assistive technologies are tools you can use to modify your desktop experience<br /> Accessed by opening the system menu and navigate to preferences, assistive technologies<br /> <br /> <br /> '''Linux Performance'''<br /> <br /> Monitor system performance using command-line included in the sysstat package.<br /> To make it easier to identify performance problems, a network administrator should run performance utilities on healthy Linux systems to develop a baseline.<br /> <br /> '''Performance Problems:'''<br /> *Software<br /> *Hardware<br /> *Combination of the two<br /> <br /> '''Software Problems'''<br /> <br /> Software that requires too many system resources may use CPU, memory, and peripheral devices creating poor performance.<br /> Too many processes running or rouge processes<br /> <br /> '''Hardware Problems'''<br /> <br /> Improperly configured hardware (May still Work)<br /> Old ( Most companies retire computer equipment after two to five years of use)<br /> Jabbering: Sending large amounts of information to the CPU when not in use.<br /> <br /> '''Resolutions'''<br /> <br /> Software problems can sometimes be resolved by changing hardware.<br /> Move or Remove the software<br /> Upgrading or adding another CPU<br /> Use bus mastering peripheral components (Devices that can perform processes normally performed by the CPU)<br /> Adding RAM to increase system speed<br /> Replace slower disk drives with faster ones<br /> Use disk striping RAID<br /> Keep CD and DVD drives on a separate hard disk controller<br /> <br /> '''Monitoring Performance with sysstat Utilities'''<br /> <br /> Using information from the /proc directory and system devices, the System Statistics (sysstat) package contains utilities that monitor the system.<br /> To install the latest version of sysstat on a Linux system, use the following method:<br /> 1. yum install sysstat <br /> <br /> '''Three of the System Statistics (sysstat) package performance monitoring utilities include:'''<br /> *mpstat (multiple processor statistics) command<br /> *iostat (input/output statistics)<br /> *sar (system activity reported) command<br /> <br /> '''mpstat (multiple processor statistics)'''<br /> <br /> Used to monitor CPU performance for all processors on the system since the system was started or rebooted.<br /> <br /> ''To monitor a single cpu use the –P option followed by the processor number.'' <br /> <br /> Example: mpstat –P 0 would display the first processor on the system.<br /> Limited in abilities<br /> <br /> <br /> '''Examining the Output of the mpstat command'''<br /> <br /> *%user= % of time the processor spent executing user programs and daemons<br /> *%nice= % of time the processor spent executing programs and daemons that had nondefault nice values <br /> *%sys= % of time the processor spent maintaining itself<br /> *%iowait= % of time the CPU was idle when an outstanding disk I/O request existed.<br /> *%irq= % of time the CPU is using to respond to normal interrupts that span multiple CPUs. <br /> *%soft= % of time the CPU is using to respond to normal interrupts that span multiple CPUs<br /> *%steal= % of time the CPU is waiting to respond to virtual CPU requests <br /> *%guest= % of time the CPU is executing another virtual CPU<br /> *%idle= % of time the CPU did not spend executing tasks. Should be greater than 25% over a long period of time. <br /> <br /> '''iostat (input/output statistics)'''<br /> <br /> Measusres the flow of information to and from disk devices.<br /> Displays CPU statistics similar to mpstat<br /> Limited in abilities<br /> Adds transfers per second (tps) and block <br /> <br /> '''sar (system activity reporter)'''<br /> <br /> Displays more information than the mpstat or iostat command<br /> Displays CPU statistics by default<br /> Most widely used performance monitoring tool on UNIX and Linux systems<br /> Scheduled using the cron daemon to run every 10 minutes for the current day<br /> logged to a file in the /var/log/sa directory called sa#. The # represents the day of the month<br /> Only one month of records is kept but can be changed by editing the cron table located at /etc/cron.d/sysstat<br /> Can display different statistics by specifying options<br /> sar (system activity reporter)<br /> Displays more information than the mpstat or iostat command<br /> Displays CPU statistics by default<br /> Most widely used performance monitoring tool on UNIX and Linux systems<br /> Scheduled using the cron daemon to run every 10 minutes for the current day<br /> logged to a file in the /var/log/sa directory called sa#. The # represents the day of the month<br /> Only one month of records is kept but can be changed by editing the cron table located at /etc/cron.d/sysstat<br /> Can display different statistics by specifying options<br /> <br /> '''Common options with the sar caommand'''<br /> <br /> *CPU Usage of ALL CPUs (sar -u) Default<br /> *CPU Usage of Individual CPU or Core (sar -P)<br /> *Memory Free and Used (sar -r)<br /> *Display swapping statistics (sar -W)<br /> *Reports run queue and load average (sar -q)<br /> *sar -u 1 3 Displays real time CPU usage every 1 second for 3 times.<br /> <br /> '''Other Performance Monitoring Utilities'''<br /> <br /> *top utility (discussed in Chapter 9)<br /> *free command can be used to display the total amounts of physical and swap memory (in Kilobytes) and their utilizations.<br /> *vmstat command indicates more information than the free command to indicate whether more physical memory is required.</div>

Powe0122 https://wiki.ihitc.net/mediawiki/index.php?title=Chapter_14_Study_Guide&diff=5487 2012-04-11T02:07:49Z

<p>Powe0122: </p> <hr /> <div>'''Linux Performance'''<br /> <br /> Monitor system performance using command-line included in the sysstat package.<br /> To make it easier to identify performance problems, a network administrator should run performance utilities on healthy Linux systems to develop a baseline.<br /> <br /> '''Performance Problems:'''<br /> *Software<br /> *Hardware<br /> *Combination of the two<br /> <br /> '''Software Problems'''<br /> <br /> Software that requires too many system resources may use CPU, memory, and peripheral devices creating poor performance.<br /> Too many processes running or rouge processes<br /> <br /> '''Hardware Problems'''<br /> <br /> Improperly configured hardware (May still Work)<br /> Old ( Most companies retire computer equipment after two to five years of use)<br /> Jabbering: Sending large amounts of information to the CPU when not in use.<br /> <br /> '''Resolutions'''<br /> <br /> Software problems can sometimes be resolved by changing hardware.<br /> Move or Remove the software<br /> Upgrading or adding another CPU<br /> Use bus mastering peripheral components (Devices that can perform processes normally performed by the CPU)<br /> Adding RAM to increase system speed<br /> Replace slower disk drives with faster ones<br /> Use disk striping RAID<br /> Keep CD and DVD drives on a separate hard disk controller<br /> <br /> '''Monitoring Performance with sysstat Utilities'''<br /> <br /> Using information from the /proc directory and system devices, the System Statistics (sysstat) package contains utilities that monitor the system.<br /> To install the latest version of sysstat on a Linux system, use the following method:<br /> 1. yum install sysstat <br /> <br /> '''Three of the System Statistics (sysstat) package performance monitoring utilities include:'''<br /> *mpstat (multiple processor statistics) command<br /> *iostat (input/output statistics)<br /> *sar (system activity reported) command<br /> <br /> '''mpstat (multiple processor statistics)'''<br /> <br /> Used to monitor CPU performance for all processors on the system since the system was started or rebooted.<br /> <br /> ''To monitor a single cpu use the –P option followed by the processor number.'' <br /> <br /> Example: mpstat –P 0 would display the first processor on the system.<br /> Limited in abilities<br /> <br /> <br /> '''Examining the Output of the mpstat command'''<br /> <br /> *%user= % of time the processor spent executing user programs and daemons<br /> *%nice= % of time the processor spent executing programs and daemons that had nondefault nice values <br /> *%sys= % of time the processor spent maintaining itself<br /> *%iowait= % of time the CPU was idle when an outstanding disk I/O request existed.<br /> *%irq= % of time the CPU is using to respond to normal interrupts that span multiple CPUs. <br /> *%soft= % of time the CPU is using to respond to normal interrupts that span multiple CPUs<br /> *%steal= % of time the CPU is waiting to respond to virtual CPU requests <br /> *%guest= % of time the CPU is executing another virtual CPU<br /> *%idle= % of time the CPU did not spend executing tasks. Should be greater than 25% over a long period of time. <br /> <br /> '''iostat (input/output statistics)'''<br /> <br /> Measusres the flow of information to and from disk devices.<br /> Displays CPU statistics similar to mpstat<br /> Limited in abilities<br /> Adds transfers per second (tps) and block <br /> <br /> '''sar (system activity reporter)'''<br /> <br /> Displays more information than the mpstat or iostat command<br /> Displays CPU statistics by default<br /> Most widely used performance monitoring tool on UNIX and Linux systems<br /> Scheduled using the cron daemon to run every 10 minutes for the current day<br /> logged to a file in the /var/log/sa directory called sa#. The # represents the day of the month<br /> Only one month of records is kept but can be changed by editing the cron table located at /etc/cron.d/sysstat<br /> Can display different statistics by specifying options<br /> sar (system activity reporter)<br /> Displays more information than the mpstat or iostat command<br /> Displays CPU statistics by default<br /> Most widely used performance monitoring tool on UNIX and Linux systems<br /> Scheduled using the cron daemon to run every 10 minutes for the current day<br /> logged to a file in the /var/log/sa directory called sa#. The # represents the day of the month<br /> Only one month of records is kept but can be changed by editing the cron table located at /etc/cron.d/sysstat<br /> Can display different statistics by specifying options<br /> <br /> '''Common options with the sar caommand'''<br /> <br /> *CPU Usage of ALL CPUs (sar -u) Default<br /> *CPU Usage of Individual CPU or Core (sar -P)<br /> *Memory Free and Used (sar -r)<br /> *Display swapping statistics (sar -W)<br /> *Reports run queue and load average (sar -q)<br /> *sar -u 1 3 Displays real time CPU usage every 1 second for 3 times.<br /> <br /> '''Other Performance Monitoring Utilities'''<br /> <br /> *top utility (discussed in Chapter 9)<br /> *free command can be used to display the total amounts of physical and swap memory (in Kilobytes) and their utilizations.<br /> *vmstat command indicates more information than the free command to indicate whether more physical memory is required.</div>

Powe0122 https://wiki.ihitc.net/mediawiki/index.php?title=File:Picture1.jpg&diff=5486 2012-04-11T02:02:22Z

<p>Powe0122: </p> <hr /> <div></div>

Powe0122 https://wiki.ihitc.net/mediawiki/index.php?title=Chapter_14_Study_Guide&diff=5485 2012-04-11T01:54:20Z

<p>Powe0122: </p> <hr /> <div>'''Linux Performance'''<br /> <br /> Monitor system performance using command-line included in the sysstat package.<br /> To make it easier to identify performance problems, a network administrator should run performance utilities on healthy Linux systems to develop a baseline.<br /> <br /> '''Performance Problems:'''<br /> *Software<br /> *Hardware<br /> *Combination of the two<br /> <br /> '''Software Problems'''<br /> <br /> Software that requires too many system resources may use CPU, memory, and peripheral devices creating poor performance.<br /> Too many processes running or rouge processes<br /> <br /> '''Hardware Problems'''<br /> <br /> Improperly configured hardware (May still Work)<br /> Old ( Most companies retire computer equipment after two to five years of use)<br /> Jabbering: Sending large amounts of information to the CPU when not in use.<br /> <br /> '''Resolutions'''<br /> <br /> Software problems can sometimes be resolved by changing hardware.<br /> Move or Remove the software<br /> Upgrading or adding another CPU<br /> Use bus mastering peripheral components (Devices that can perform processes normally performed by the CPU)<br /> Adding RAM to increase system speed<br /> Replace slower disk drives with faster ones<br /> Use disk striping RAID<br /> Keep CD and DVD drives on a separate hard disk controller<br /> <br /> '''Monitoring Performance with sysstat Utilities'''<br /> <br /> Using information from the /proc directory and system devices, the System Statistics (sysstat) package contains utilities that monitor the system.<br /> To install the latest version of sysstat on a Linux system, use the following method:<br /> 1. yum install sysstat <br /> <br /> '''Three of the System Statistics (sysstat) package performance monitoring utilities include:'''<br /> *mpstat (multiple processor statistics) command<br /> *iostat (input/output statistics)<br /> *sar (system activity reported) command<br /> <br /> '''mpstat (multiple processor statistics)'''<br /> <br /> Used to monitor CPU performance for all processors on the system since the system was started or rebooted.<br /> <br /> ''To monitor a single cpu use the –P option followed by the processor number.'' <br /> <br /> Example: mpstat –P 0 would display the first processor on the system.<br /> Limited in abilities<br /> <br /> <br /> '''Examining the Output of the mpstat command'''<br /> <br /> *%user= % of time the processor spent executing user programs and daemons<br /> *%nice= % of time the processor spent executing programs and daemons that had nondefault nice values <br /> *%sys= % of time the processor spent maintaining itself<br /> *%iowait= % of time the CPU was idle when an outstanding disk I/O request existed.<br /> *%irq= % of time the CPU is using to respond to normal interrupts that span multiple CPUs. <br /> *%soft= % of time the CPU is using to respond to normal interrupts that span multiple CPUs<br /> *%steal= % of time the CPU is waiting to respond to virtual CPU requests <br /> *%guest= % of time the CPU is executing another virtual CPU<br /> *%idle= % of time the CPU did not spend executing tasks. Should be greater than 25% over a long period of time. <br /> <br /> '''iostat (input/output statistics)'''<br /> <br /> Measusres the flow of information to and from disk devices.<br /> Displays CPU statistics similar to mpstat<br /> Limited in abilities<br /> Adds transfers per second (tps) and block <br /> <br /> '''sar (system activity reporter)'''<br /> <br /> Displays more information than the mpstat or iostat command<br /> Displays CPU statistics by default<br /> Most widely used performance monitoring tool on UNIX and Linux systems<br /> Scheduled using the cron daemon to run every 10 minutes for the current day<br /> logged to a file in the /var/log/sa directory called sa#. The # represents the day of the month<br /> Only one month of records is kept but can be changed by editing the cron table located at /etc/cron.d/sysstat<br /> Can display different statistics by specifying options<br /> sar (system activity reporter)<br /> Displays more information than the mpstat or iostat command<br /> Displays CPU statistics by default<br /> Most widely used performance monitoring tool on UNIX and Linux systems<br /> Scheduled using the cron daemon to run every 10 minutes for the current day<br /> logged to a file in the /var/log/sa directory called sa#. The # represents the day of the month<br /> Only one month of records is kept but can be changed by editing the cron table located at /etc/cron.d/sysstat<br /> Can display different statistics by specifying options<br /> <br /> '''Common options with the sar caommand'''<br /> <br /> CPU Usage of ALL CPUs (sar -u) Default<br /> CPU Usage of Individual CPU or Core (sar -P)<br /> Memory Free and Used (sar -r)<br /> Display swapping statistics (sar -W)<br /> Reports run queue and load average (sar -q)<br /> sar -u 1 3 Displays real time CPU usage every 1 second for 3 times.<br /> <br /> '''Other Performance Monitoring Utilities'''<br /> <br /> *top utility (discussed in Chapter 9)<br /> *free command can be used to display the total amounts of physical and swap memory (in Kilobytes) and their utilizations.<br /> *vmstat command indicates more information than the free command to indicate whether more physical memory is required.</div>

Powe0122 https://wiki.ihitc.net/mediawiki/index.php?title=Chapter_14_Study_Guide&diff=5484 2012-04-11T01:51:14Z

<p>Powe0122: </p> <hr /> <div>'''Linux Performance'''<br /> <br /> Monitor system performance using command-line included in the sysstat package.<br /> To make it easier to identify performance problems, a network administrator should run performance utilities on healthy Linux systems to develop a baseline.<br /> <br /> '''Performance Problems:'''<br /> *Software<br /> *Hardware<br /> *Combination of the two<br /> <br /> '''Software Problems'''<br /> <br /> Software that requires too many system resources may use CPU, memory, and peripheral devices creating poor performance.<br /> Too many processes running or rouge processes<br /> <br /> '''Hardware Problems'''<br /> <br /> Improperly configured hardware (May still Work)<br /> Old ( Most companies retire computer equipment after two to five years of use)<br /> Jabbering: Sending large amounts of information to the CPU when not in use.<br /> <br /> '''Resolutions'''<br /> <br /> Software problems can sometimes be resolved by changing hardware.<br /> Move or Remove the software<br /> Upgrading or adding another CPU<br /> Use bus mastering peripheral components (Devices that can perform processes normally performed by the CPU)<br /> Adding RAM to increase system speed<br /> Replace slower disk drives with faster ones<br /> Use disk striping RAID<br /> Keep CD and DVD drives on a separate hard disk controller<br /> <br /> '''Monitoring Performance with sysstat Utilities'''<br /> <br /> Using information from the /proc directory and system devices, the System Statistics (sysstat) package contains utilities that monitor the system.<br /> To install the latest version of sysstat on a Linux system, use the following method:<br /> 1. yum install sysstat <br /> <br /> '''Three of the System Statistics (sysstat) package performance monitoring utilities include:'''<br /> *mpstat (multiple processor statistics) command<br /> *iostat (input/output statistics)<br /> *sar (system activity reported) command<br /> <br /> '''mpstat (multiple processor statistics)'''<br /> <br /> Used to monitor CPU performance for all processors on the system since the system was started or rebooted.<br /> <br /> ''To monitor a single cpu use the –P option followed by the processor number.'' <br /> <br /> Example: mpstat –P 0 would display the first processor on the system.<br /> Limited in abilities<br /> <br /> [[File:Example.jpg]]<br /> <br /> '''Examining the Output of the mpstat command'''<br /> <br /> *%user= % of time the processor spent executing user programs and daemons<br /> *%nice= % of time the processor spent executing programs and daemons that had nondefault nice values <br /> *%sys= % of time the processor spent maintaining itself<br /> *%iowait= % of time the CPU was idle when an outstanding disk I/O request existed.<br /> *%irq= % of time the CPU is using to respond to normal interrupts that span multiple CPUs. <br /> *%soft= % of time the CPU is using to respond to normal interrupts that span multiple CPUs<br /> *%steal= % of time the CPU is waiting to respond to virtual CPU requests <br /> *%guest= % of time the CPU is executing another virtual CPU<br /> *%idle= % of time the CPU did not spend executing tasks. Should be greater than 25% over a long period of time. <br /> <br /> '''iostat (input/output statistics)'''<br /> <br /> Measusres the flow of information to and from disk devices.<br /> Displays CPU statistics similar to mpstat<br /> Limited in abilities<br /> Adds transfers per second (tps) and block <br /> <br /> '''sar (system activity reporter)'''<br /> <br /> Displays more information than the mpstat or iostat command<br /> Displays CPU statistics by default<br /> Most widely used performance monitoring tool on UNIX and Linux systems<br /> Scheduled using the cron daemon to run every 10 minutes for the current day<br /> logged to a file in the /var/log/sa directory called sa#. The # represents the day of the month<br /> Only one month of records is kept but can be changed by editing the cron table located at /etc/cron.d/sysstat<br /> Can display different statistics by specifying options<br /> sar (system activity reporter)<br /> Displays more information than the mpstat or iostat command<br /> Displays CPU statistics by default<br /> Most widely used performance monitoring tool on UNIX and Linux systems<br /> Scheduled using the cron daemon to run every 10 minutes for the current day<br /> logged to a file in the /var/log/sa directory called sa#. The # represents the day of the month<br /> Only one month of records is kept but can be changed by editing the cron table located at /etc/cron.d/sysstat<br /> Can display different statistics by specifying options<br /> <br /> '''Common options with the sar caommand'''<br /> <br /> CPU Usage of ALL CPUs (sar -u) Default<br /> CPU Usage of Individual CPU or Core (sar -P)<br /> Memory Free and Used (sar -r)<br /> Display swapping statistics (sar -W)<br /> Reports run queue and load average (sar -q)<br /> sar -u 1 3 Displays real time CPU usage every 1 second for 3 times.<br /> <br /> '''Other Performance Monitoring Utilities'''<br /> <br /> *top utility (discussed in Chapter 9)<br /> *free command can be used to display the total amounts of physical and swap memory (in Kilobytes) and their utilizations.<br /> *vmstat command indicates more information than the free command to indicate whether more physical memory is required.</div>

Powe0122 https://wiki.ihitc.net/mediawiki/index.php?title=Chapter_14_Study_Guide&diff=5483 2012-04-11T01:49:02Z

<p>Powe0122: </p> <hr /> <div>'''Linux Performance'''<br /> <br /> Monitor system performance using command-line included in the sysstat package.<br /> To make it easier to identify performance problems, a network administrator should run performance utilities on healthy Linux systems to develop a baseline.<br /> <br /> '''Performance Problems:'''<br /> *Software<br /> *Hardware<br /> *Combination of the two<br /> <br /> '''Software Problems'''<br /> <br /> Software that requires too many system resources may use CPU, memory, and peripheral devices creating poor performance.<br /> Too many processes running or rouge processes<br /> <br /> '''Hardware Problems'''<br /> <br /> Improperly configured hardware (May still Work)<br /> Old ( Most companies retire computer equipment after two to five years of use)<br /> Jabbering: Sending large amounts of information to the CPU when not in use.<br /> <br /> '''Resolutions'''<br /> <br /> Software problems can sometimes be resolved by changing hardware.<br /> Move or Remove the software<br /> Upgrading or adding another CPU<br /> Use bus mastering peripheral components (Devices that can perform processes normally performed by the CPU)<br /> Adding RAM to increase system speed<br /> Replace slower disk drives with faster ones<br /> Use disk striping RAID<br /> Keep CD and DVD drives on a separate hard disk controller<br /> <br /> '''Monitoring Performance with sysstat Utilities'''<br /> <br /> Using information from the /proc directory and system devices, the System Statistics (sysstat) package contains utilities that monitor the system.<br /> To install the latest version of sysstat on a Linux system, use the following method:<br /> 1. yum install sysstat <br /> <br /> '''Three of the System Statistics (sysstat) package performance monitoring utilities include:'''<br /> *mpstat (multiple processor statistics) command<br /> *iostat (input/output statistics)<br /> *sar (system activity reported) command<br /> <br /> '''mpstat (multiple processor statistics)'''<br /> <br /> Used to monitor CPU performance for all processors on the system since the system was started or rebooted.<br /> <br /> ''To monitor a single cpu use the –P option followed by the processor number.'' <br /> <br /> Example: mpstat –P 0 would display the first processor on the system.<br /> Limited in abilities<br /> <br /> '''Examining the Output of the mpstat command'''<br /> <br /> *%user= % of time the processor spent executing user programs and daemons<br /> *%nice= % of time the processor spent executing programs and daemons that had nondefault nice values <br /> *%sys= % of time the processor spent maintaining itself<br /> *%iowait= % of time the CPU was idle when an outstanding disk I/O request existed.<br /> *%irq= % of time the CPU is using to respond to normal interrupts that span multiple CPUs. <br /> *%soft= % of time the CPU is using to respond to normal interrupts that span multiple CPUs<br /> *%steal= % of time the CPU is waiting to respond to virtual CPU requests <br /> *%guest= % of time the CPU is executing another virtual CPU<br /> *%idle= % of time the CPU did not spend executing tasks. Should be greater than 25% over a long period of time. <br /> <br /> '''iostat (input/output statistics)'''<br /> <br /> Measusres the flow of information to and from disk devices.<br /> Displays CPU statistics similar to mpstat<br /> Limited in abilities<br /> Adds transfers per second (tps) and block <br /> <br /> '''sar (system activity reporter)'''<br /> <br /> Displays more information than the mpstat or iostat command<br /> Displays CPU statistics by default<br /> Most widely used performance monitoring tool on UNIX and Linux systems<br /> Scheduled using the cron daemon to run every 10 minutes for the current day<br /> logged to a file in the /var/log/sa directory called sa#. The # represents the day of the month<br /> Only one month of records is kept but can be changed by editing the cron table located at /etc/cron.d/sysstat<br /> Can display different statistics by specifying options<br /> sar (system activity reporter)<br /> Displays more information than the mpstat or iostat command<br /> Displays CPU statistics by default<br /> Most widely used performance monitoring tool on UNIX and Linux systems<br /> Scheduled using the cron daemon to run every 10 minutes for the current day<br /> logged to a file in the /var/log/sa directory called sa#. The # represents the day of the month<br /> Only one month of records is kept but can be changed by editing the cron table located at /etc/cron.d/sysstat<br /> Can display different statistics by specifying options<br /> <br /> '''Common options with the sar caommand'''<br /> <br /> CPU Usage of ALL CPUs (sar -u) Default<br /> CPU Usage of Individual CPU or Core (sar -P)<br /> Memory Free and Used (sar -r)<br /> Display swapping statistics (sar -W)<br /> Reports run queue and load average (sar -q)<br /> sar -u 1 3 Displays real time CPU usage every 1 second for 3 times.<br /> <br /> '''Other Performance Monitoring Utilities'''<br /> <br /> *top utility (discussed in Chapter 9)<br /> *free command can be used to display the total amounts of physical and swap memory (in Kilobytes) and their utilizations.<br /> *vmstat command indicates more information than the free command to indicate whether more physical memory is required.</div>

Powe0122 https://wiki.ihitc.net/mediawiki/index.php?title=Chapter_14_Study_Guide&diff=5482 2012-04-11T01:47:33Z

<p>Powe0122: </p> <hr /> <div>'''Linux Performance'''<br /> <br /> Monitor system performance using command-line included in the sysstat package.<br /> To make it easier to identify performance problems, a network administrator should run performance utilities on healthy Linux systems to develop a baseline.<br /> <br /> '''Performance Problems:'''<br /> *Software<br /> *Hardware<br /> *Combination of the two<br /> <br /> '''Software Problems'''<br /> <br /> Software that requires too many system resources may use CPU, memory, and peripheral devices creating poor performance.<br /> Too many processes running or rouge processes<br /> <br /> '''Hardware Problems'''<br /> <br /> Improperly configured hardware (May still Work)<br /> Old ( Most companies retire computer equipment after two to five years of use)<br /> Jabbering: Sending large amounts of information to the CPU when not in use.<br /> <br /> '''Resolutions'''<br /> <br /> Software problems can sometimes be resolved by changing hardware.<br /> Move or Remove the software<br /> Upgrading or adding another CPU<br /> Use bus mastering peripheral components (Devices that can perform processes normally performed by the CPU)<br /> Adding RAM to increase system speed<br /> Replace slower disk drives with faster ones<br /> Use disk striping RAID<br /> Keep CD and DVD drives on a separate hard disk controller<br /> <br /> '''Monitoring Performance with sysstat Utilities'''<br /> <br /> Using information from the /proc directory and system devices, the System Statistics (sysstat) package contains utilities that monitor the system.<br /> To install the latest version of sysstat on a Linux system, use the following method:<br /> 1. yum install sysstat <br /> <br /> '''Three of the System Statistics (sysstat) package performance monitoring utilities include:'''<br /> *mpstat (multiple processor statistics) command<br /> *iostat (input/output statistics)<br /> *sar (system activity reported) command<br /> <br /> '''mpstat (multiple processor statistics)'''<br /> <br /> Used to monitor CPU performance for all processors on the system since the system was started or rebooted.<br /> <br /> ''To monitor a single cpu use the –P option followed by the processor number.'' <br /> <br /> Example: mpstat –P 0 would display the first processor on the system.<br /> Limited in abilities<br /> <br /> '''Examining the Output of the mpstat command'''<br /> <br /> %user= % of time the processor spent executing user programs and daemons<br /> %nice= % of time the processor spent executing programs and daemons that had nondefault nice values <br /> %sys= % of time the processor spent maintaining itself<br /> %iowait= % of time the CPU was idle when an outstanding disk I/O request existed.<br /> %irq= % of time the CPU is using to respond to normal interrupts that span multiple CPUs. <br /> %soft= % of time the CPU is using to respond to normal interrupts that span multiple CPUs<br /> %steal= % of time the CPU is waiting to respond to virtual CPU requests <br /> %guest= % of time the CPU is executing another virtual CPU<br /> %idle= % of time the CPU did not spend executing tasks. Should be greater than 25% over a long period of time. <br /> <br /> '''iostat (input/output statistics)'''<br /> <br /> Measusres the flow of information to and from disk devices.<br /> Displays CPU statistics similar to mpstat<br /> Limited in abilities<br /> Adds transfers per second (tps) and block <br /> <br /> '''sar (system activity reporter)'''<br /> <br /> Displays more information than the mpstat or iostat command<br /> Displays CPU statistics by default<br /> Most widely used performance monitoring tool on UNIX and Linux systems<br /> Scheduled using the cron daemon to run every 10 minutes for the current day<br /> logged to a file in the /var/log/sa directory called sa#. The # represents the day of the month<br /> Only one month of records is kept but can be changed by editing the cron table located at /etc/cron.d/sysstat<br /> Can display different statistics by specifying options<br /> sar (system activity reporter)<br /> Displays more information than the mpstat or iostat command<br /> Displays CPU statistics by default<br /> Most widely used performance monitoring tool on UNIX and Linux systems<br /> Scheduled using the cron daemon to run every 10 minutes for the current day<br /> logged to a file in the /var/log/sa directory called sa#. The # represents the day of the month<br /> Only one month of records is kept but can be changed by editing the cron table located at /etc/cron.d/sysstat<br /> Can display different statistics by specifying options<br /> <br /> '''Common options with the sar caommand'''<br /> <br /> CPU Usage of ALL CPUs (sar -u) Default<br /> CPU Usage of Individual CPU or Core (sar -P)<br /> Memory Free and Used (sar -r)<br /> Display swapping statistics (sar -W)<br /> Reports run queue and load average (sar -q)<br /> sar -u 1 3 Displays real time CPU usage every 1 second for 3 times.<br /> <br /> '''Other Performance Monitoring Utilities'''<br /> <br /> *top utility (discussed in Chapter 9)<br /> *free command can be used to display the total amounts of physical and swap memory (in Kilobytes) and their utilizations.<br /> *vmstat command indicates more information than the free command to indicate whether more physical memory is required.</div>

Powe0122 https://wiki.ihitc.net/mediawiki/index.php?title=Chapter_14_Study_Guide&diff=5481 2012-04-11T01:46:31Z

<p>Powe0122: </p> <hr /> <div>'''Linux Performance'''<br /> <br /> Monitor system performance using command-line included in the sysstat package.<br /> To make it easier to identify performance problems, a network administrator should run performance utilities on healthy Linux systems to develop a baseline.<br /> Performance Problems:<br /> Software<br /> Hardware<br /> Combination of the two<br /> <br /> '''Software Problems'''<br /> <br /> Software that requires too many system resources may use CPU, memory, and peripheral devices creating poor performance.<br /> Too many processes running or rouge processes<br /> <br /> '''Hardware Problems'''<br /> <br /> Improperly configured hardware (May still Work)<br /> Old ( Most companies retire computer equipment after two to five years of use)<br /> Jabbering: Sending large amounts of information to the CPU when not in use.<br /> <br /> '''Resolutions'''<br /> <br /> Software problems can sometimes be resolved by changing hardware.<br /> Move or Remove the software<br /> Upgrading or adding another CPU<br /> Use bus mastering peripheral components (Devices that can perform processes normally performed by the CPU)<br /> Adding RAM to increase system speed<br /> Replace slower disk drives with faster ones<br /> Use disk striping RAID<br /> Keep CD and DVD drives on a separate hard disk controller<br /> <br /> '''Monitoring Performance with sysstat Utilities'''<br /> <br /> Using information from the /proc directory and system devices, the System Statistics (sysstat) package contains utilities that monitor the system.<br /> To install the latest version of sysstat on a Linux system, use the following method:<br /> 1. yum install sysstat <br /> <br /> '''Three of the System Statistics (sysstat) package performance monitoring utilities include:'''<br /> *mpstat (multiple processor statistics) command<br /> *iostat (input/output statistics)<br /> *sar (system activity reported) command<br /> <br /> '''mpstat (multiple processor statistics)'''<br /> <br /> Used to monitor CPU performance for all processors on the system since the system was started or rebooted.<br /> <br /> ''To monitor a single cpu use the –P option followed by the processor number.'' <br /> <br /> Example: mpstat –P 0 would display the first processor on the system.<br /> Limited in abilities<br /> <br /> '''Examining the Output of the mpstat command'''<br /> <br /> %user= % of time the processor spent executing user programs and daemons<br /> %nice= % of time the processor spent executing programs and daemons that had nondefault nice values <br /> %sys= % of time the processor spent maintaining itself<br /> %iowait= % of time the CPU was idle when an outstanding disk I/O request existed.<br /> %irq= % of time the CPU is using to respond to normal interrupts that span multiple CPUs. <br /> %soft= % of time the CPU is using to respond to normal interrupts that span multiple CPUs<br /> %steal= % of time the CPU is waiting to respond to virtual CPU requests <br /> %guest= % of time the CPU is executing another virtual CPU<br /> %idle= % of time the CPU did not spend executing tasks. Should be greater than 25% over a long period of time. <br /> <br /> '''iostat (input/output statistics)'''<br /> <br /> Measusres the flow of information to and from disk devices.<br /> Displays CPU statistics similar to mpstat<br /> Limited in abilities<br /> Adds transfers per second (tps) and block <br /> <br /> '''sar (system activity reporter)'''<br /> <br /> Displays more information than the mpstat or iostat command<br /> Displays CPU statistics by default<br /> Most widely used performance monitoring tool on UNIX and Linux systems<br /> Scheduled using the cron daemon to run every 10 minutes for the current day<br /> logged to a file in the /var/log/sa directory called sa#. The # represents the day of the month<br /> Only one month of records is kept but can be changed by editing the cron table located at /etc/cron.d/sysstat<br /> Can display different statistics by specifying options<br /> sar (system activity reporter)<br /> Displays more information than the mpstat or iostat command<br /> Displays CPU statistics by default<br /> Most widely used performance monitoring tool on UNIX and Linux systems<br /> Scheduled using the cron daemon to run every 10 minutes for the current day<br /> logged to a file in the /var/log/sa directory called sa#. The # represents the day of the month<br /> Only one month of records is kept but can be changed by editing the cron table located at /etc/cron.d/sysstat<br /> Can display different statistics by specifying options<br /> <br /> '''Common options with the sar caommand'''<br /> <br /> CPU Usage of ALL CPUs (sar -u) Default<br /> CPU Usage of Individual CPU or Core (sar -P)<br /> Memory Free and Used (sar -r)<br /> Display swapping statistics (sar -W)<br /> Reports run queue and load average (sar -q)<br /> sar -u 1 3 Displays real time CPU usage every 1 second for 3 times.<br /> <br /> '''Other Performance Monitoring Utilities'''<br /> <br /> *top utility (discussed in Chapter 9)<br /> *free command can be used to display the total amounts of physical and swap memory (in Kilobytes) and their utilizations.<br /> *vmstat command indicates more information than the free command to indicate whether more physical memory is required.</div>

Powe0122 https://wiki.ihitc.net/mediawiki/index.php?title=Chapter_14_Study_Guide&diff=5480 2012-04-11T01:45:50Z

<p>Powe0122: </p> <hr /> <div>'''Linux Performance'''<br /> <br /> Monitor system performance using command-line included in the sysstat package.<br /> To make it easier to identify performance problems, a network administrator should run performance utilities on healthy Linux systems to develop a baseline.<br /> Performance Problems:<br /> Software<br /> Hardware<br /> Combination of the two<br /> <br /> '''Software Problems'''<br /> <br /> Software that requires too many system resources may use CPU, memory, and peripheral devices creating poor performance.<br /> Too many processes running or rouge processes<br /> <br /> '''Hardware Problems'''<br /> <br /> Improperly configured hardware (May still Work)<br /> Old ( Most companies retire computer equipment after two to five years of use)<br /> Jabbering: Sending large amounts of information to the CPU when not in use.<br /> <br /> '''Resolutions'''<br /> <br /> Software problems can sometimes be resolved by changing hardware.<br /> Move or Remove the software<br /> Upgrading or adding another CPU<br /> Use bus mastering peripheral components (Devices that can perform processes normally performed by the CPU)<br /> Adding RAM to increase system speed<br /> Replace slower disk drives with faster ones<br /> Use disk striping RAID<br /> Keep CD and DVD drives on a separate hard disk controller<br /> <br /> '''Monitoring Performance with sysstat Utilities'''<br /> <br /> Using information from the /proc directory and system devices, the System Statistics (sysstat) package contains utilities that monitor the system.<br /> To install the latest version of sysstat on a Linux system, use the following method:<br /> 1. yum install sysstat <br /> <br /> '''Three of the System Statistics (sysstat) package performance monitoring utilities include:'''<br /> *mpstat (multiple processor statistics) command<br /> *iostat (input/output statistics)<br /> *sar (system activity reported) command<br /> <br /> '''mpstat (multiple processor statistics)'''<br /> <br /> Used to monitor CPU performance for all processors on the system since the system was started or rebooted.<br /> <br /> ''To monitor a single cpu use the –P option followed by the processor number.'' <br /> <br /> Example: mpstat –P 0 would display the first processor on the system.<br /> Limited in abilities<br /> <br /> '''Examining the Output of the mpstat command'''<br /> <br /> %user= % of time the processor spent executing user programs and daemons<br /> %nice= % of time the processor spent executing programs and daemons that had nondefault nice values <br /> %sys= % of time the processor spent maintaining itself<br /> %iowait= % of time the CPU was idle when an outstanding disk I/O request existed.<br /> %irq= % of time the CPU is using to respond to normal interrupts that span multiple CPUs. <br /> %soft= % of time the CPU is using to respond to normal interrupts that span multiple CPUs<br /> %steal= % of time the CPU is waiting to respond to virtual CPU requests <br /> %guest= % of time the CPU is executing another virtual CPU<br /> %idle= % of time the CPU did not spend executing tasks. Should be greater than 25% over a long period of time. <br /> <br /> '''iostat (input/output statistics)'''<br /> <br /> Measusres the flow of information to and from disk devices.<br /> Displays CPU statistics similar to mpstat<br /> Limited in abilities<br /> Adds transfers per second (tps) and block <br /> <br /> '''sar (system activity reporter)'''<br /> <br /> Displays more information than the mpstat or iostat command<br /> Displays CPU statistics by default<br /> Most widely used performance monitoring tool on UNIX and Linux systems<br /> Scheduled using the cron daemon to run every 10 minutes for the current day<br /> logged to a file in the /var/log/sa directory called sa#. The # represents the day of the month<br /> Only one month of records is kept but can be changed by editing the cron table located at /etc/cron.d/sysstat<br /> Can display different statistics by specifying options<br /> sar (system activity reporter)<br /> Displays more information than the mpstat or iostat command<br /> Displays CPU statistics by default<br /> Most widely used performance monitoring tool on UNIX and Linux systems<br /> Scheduled using the cron daemon to run every 10 minutes for the current day<br /> logged to a file in the /var/log/sa directory called sa#. The # represents the day of the month<br /> Only one month of records is kept but can be changed by editing the cron table located at /etc/cron.d/sysstat<br /> Can display different statistics by specifying options<br /> <br /> '''Common options with the sar caommand'''<br /> <br /> CPU Usage of ALL CPUs (sar -u) Default<br /> CPU Usage of Individual CPU or Core (sar -P)<br /> Memory Free and Used (sar -r)<br /> Display swapping statistics (sar -W)<br /> Reports run queue and load average (sar -q)<br /> sar -u 1 3 Displays real time CPU usage every 1 second for 3 times.<br /> <br /> '''Other Performance Monitoring Utilities'''<br /> <br /> top utility (discussed in Chapter 9)<br /> free command can be used to display the total amounts of physical and swap memory (in Kilobytes) and their utilizations.<br /> vmstat command indicates more information than the free command to indicate whether more physical memory is required.</div>

Powe0122 https://wiki.ihitc.net/mediawiki/index.php?title=Chapter_14_Study_Guide&diff=5479 2012-04-11T01:44:37Z

<p>Powe0122: </p> <hr /> <div>'''Linux Performance'''<br /> <br /> Monitor system performance using command-line included in the sysstat package.<br /> To make it easier to identify performance problems, a network administrator should run performance utilities on healthy Linux systems to develop a baseline.<br /> Performance Problems:<br /> Software<br /> Hardware<br /> Combination of the two<br /> <br /> '''Software Problems'''<br /> Software that requires too many system resources may use CPU, memory, and peripheral devices creating poor performance.<br /> Too many processes running or rouge processes<br /> <br /> '''Hardware Problems'''<br /> Improperly configured hardware (May still Work)<br /> Old ( Most companies retire computer equipment after two to five years of use)<br /> Jabbering: Sending large amounts of information to the CPU when not in use.<br /> <br /> '''Resolutions'''<br /> Software problems can sometimes be resolved by changing hardware.<br /> Move or Remove the software<br /> Upgrading or adding another CPU<br /> Use bus mastering peripheral components (Devices that can perform processes normally performed by the CPU)<br /> Adding RAM to increase system speed<br /> Replace slower disk drives with faster ones<br /> Use disk striping RAID<br /> Keep CD and DVD drives on a separate hard disk controller<br /> <br /> '''Monitoring Performance with sysstat Utilities'''<br /> Using information from the /proc directory and system devices, the System Statistics (sysstat) package contains utilities that monitor the system.<br /> To install the latest version of sysstat on a Linux system, use the following method:<br /> 1. yum install sysstat <br /> <br /> '''Three of the System Statistics (sysstat) package performance monitoring utilities include:'''mpstat (multiple processor statistics) command<br /> iostat (input/output statistics)<br /> sar (system activity reported) command<br /> <br /> '''mpstat (multiple processor statistics)''' <br /> Used to monitor CPU performance for all processors on the system since the system was started or rebooted.<br /> <br /> ''To monitor a single cpu use the –P option followed by the processor number.'' <br /> Example: mpstat –P 0 would display the first processor on the system.<br /> Limited in abilities<br /> <br /> '''Examining the Output of the mpstat command'''<br /> %user= % of time the processor spent executing user programs and daemons<br /> %nice= % of time the processor spent executing programs and daemons that had nondefault nice values <br /> %sys= % of time the processor spent maintaining itself<br /> %iowait= % of time the CPU was idle when an outstanding disk I/O request existed.<br /> %irq= % of time the CPU is using to respond to normal interrupts that span multiple CPUs. <br /> %soft= % of time the CPU is using to respond to normal interrupts that span multiple CPUs<br /> %steal= % of time the CPU is waiting to respond to virtual CPU requests <br /> %guest= % of time the CPU is executing another virtual CPU<br /> %idle= % of time the CPU did not spend executing tasks. Should be greater than 25% over a long period of time. <br /> <br /> '''iostat (input/output statistics)'''<br /> Measusres the flow of information to and from disk devices.<br /> Displays CPU statistics similar to mpstat<br /> Limited in abilities<br /> Adds transfers per second (tps) and block <br /> <br /> '''sar (system activity reporter)'''<br /> Displays more information than the mpstat or iostat command<br /> Displays CPU statistics by default<br /> Most widely used performance monitoring tool on UNIX and Linux systems<br /> Scheduled using the cron daemon to run every 10 minutes for the current day<br /> logged to a file in the /var/log/sa directory called sa#. The # represents the day of the month<br /> Only one month of records is kept but can be changed by editing the cron table located at /etc/cron.d/sysstat<br /> Can display different statistics by specifying options<br /> sar (system activity reporter)<br /> Displays more information than the mpstat or iostat command<br /> Displays CPU statistics by default<br /> Most widely used performance monitoring tool on UNIX and Linux systems<br /> Scheduled using the cron daemon to run every 10 minutes for the current day<br /> logged to a file in the /var/log/sa directory called sa#. The # represents the day of the month<br /> Only one month of records is kept but can be changed by editing the cron table located at /etc/cron.d/sysstat<br /> Can display different statistics by specifying options<br /> <br /> '''Common options with the sar caommand'''<br /> CPU Usage of ALL CPUs (sar -u) Default<br /> CPU Usage of Individual CPU or Core (sar -P)<br /> Memory Free and Used (sar -r)<br /> Display swapping statistics (sar -W)<br /> Reports run queue and load average (sar -q)<br /> sar -u 1 3 Displays real time CPU usage every 1 second for 3 times.<br /> <br /> '''Other Performance Monitoring Utilities'''<br /> top utility (discussed in Chapter 9)<br /> free command can be used to display the total amounts of physical and swap memory (in Kilobytes) and their utilizations.<br /> vmstat command indicates more information than the free command to indicate whether more physical memory is required.</div>

Powe0122 https://wiki.ihitc.net/mediawiki/index.php?title=Chapter_14_Study_Guide&diff=5478 2012-04-11T01:42:18Z

<p>Powe0122: Created page with &quot;&#039;&#039;&#039;Linux Performance&#039;&#039;&#039; Monitor system performance using command-line included in the sysstat package. To make it easier to identify performance problems, a network administrator...&quot;</p> <hr /> <div>'''Linux Performance'''<br /> Monitor system performance using command-line included in the sysstat package.<br /> To make it easier to identify performance problems, a network administrator should run performance utilities on healthy Linux systems to develop a baseline.<br /> Performance Problems:<br /> Software<br /> Hardware<br /> Combination of the two<br /> <br /> '''Software Problems'''<br /> Software that requires too many system resources may use CPU, memory, and peripheral devices creating poor performance.<br /> Too many processes running or rouge processes<br /> <br /> '''Hardware Problems'''<br /> Improperly configured hardware (May still Work)<br /> Old ( Most companies retire computer equipment after two to five years of use)<br /> Jabbering: Sending large amounts of information to the CPU when not in use.<br /> <br /> '''Resolutions'''<br /> Software problems can sometimes be resolved by changing hardware.<br /> Move or Remove the software<br /> Upgrading or adding another CPU<br /> Use bus mastering peripheral components (Devices that can perform processes normally performed by the CPU)<br /> Adding RAM to increase system speed<br /> Replace slower disk drives with faster ones<br /> Use disk striping RAID<br /> Keep CD and DVD drives on a separate hard disk controller<br /> <br /> '''Monitoring Performance with sysstat Utilities'''<br /> Using information from the /proc directory and system devices, the System Statistics (sysstat) package contains utilities that monitor the system.<br /> To install the latest version of sysstat on a Linux system, use the following method:<br /> 1. yum install sysstat <br /> <br /> '''Three of the System Statistics (sysstat) package performance monitoring utilities include:'''mpstat (multiple processor statistics) command<br /> iostat (input/output statistics)<br /> sar (system activity reported) command<br /> <br /> '''mpstat (multiple processor statistics)''' <br /> Used to monitor CPU performance for all processors on the system since the system was started or rebooted.<br /> <br /> ''To monitor a single cpu use the –P option followed by the processor number.'' <br /> Example: mpstat –P 0 would display the first processor on the system.<br /> Limited in abilities<br /> <br /> '''Examining the Output of the mpstat command'''<br /> %user= % of time the processor spent executing user programs and daemons<br /> %nice= % of time the processor spent executing programs and daemons that had nondefault nice values <br /> %sys= % of time the processor spent maintaining itself<br /> %iowait= % of time the CPU was idle when an outstanding disk I/O request existed.<br /> %irq= % of time the CPU is using to respond to normal interrupts that span multiple CPUs. <br /> %soft= % of time the CPU is using to respond to normal interrupts that span multiple CPUs<br /> %steal= % of time the CPU is waiting to respond to virtual CPU requests <br /> %guest= % of time the CPU is executing another virtual CPU<br /> %idle= % of time the CPU did not spend executing tasks. Should be greater than 25% over a long period of time. <br /> <br /> '''iostat (input/output statistics)'''<br /> Measusres the flow of information to and from disk devices.<br /> Displays CPU statistics similar to mpstat<br /> Limited in abilities<br /> Adds transfers per second (tps) and block <br /> <br /> '''sar (system activity reporter)'''<br /> Displays more information than the mpstat or iostat command<br /> Displays CPU statistics by default<br /> Most widely used performance monitoring tool on UNIX and Linux systems<br /> Scheduled using the cron daemon to run every 10 minutes for the current day<br /> logged to a file in the /var/log/sa directory called sa#. The # represents the day of the month<br /> Only one month of records is kept but can be changed by editing the cron table located at /etc/cron.d/sysstat<br /> Can display different statistics by specifying options<br /> sar (system activity reporter)<br /> Displays more information than the mpstat or iostat command<br /> Displays CPU statistics by default<br /> Most widely used performance monitoring tool on UNIX and Linux systems<br /> Scheduled using the cron daemon to run every 10 minutes for the current day<br /> logged to a file in the /var/log/sa directory called sa#. The # represents the day of the month<br /> Only one month of records is kept but can be changed by editing the cron table located at /etc/cron.d/sysstat<br /> Can display different statistics by specifying options<br /> <br /> '''Common options with the sar caommand'''<br /> CPU Usage of ALL CPUs (sar -u) Default<br /> CPU Usage of Individual CPU or Core (sar -P)<br /> Memory Free and Used (sar -r)<br /> Display swapping statistics (sar -W)<br /> Reports run queue and load average (sar -q)<br /> sar -u 1 3 Displays real time CPU usage every 1 second for 3 times.<br /> <br /> '''Other Performance Monitoring Utilities'''<br /> top utility (discussed in Chapter 9)<br /> free command can be used to display the total amounts of physical and swap memory (in Kilobytes) and their utilizations.<br /> vmstat command indicates more information than the free command to indicate whether more physical memory is required.</div>

Powe0122 https://wiki.ihitc.net/mediawiki/index.php?title=Franske_CNT-2311&diff=5477 2012-04-11T01:36:25Z

<p>Powe0122: /* Chapter Study Guides */</p> <hr /> <div>This is the homepage for the CNT-2311 classes taught by Dr. Ben Franske.<br /> <br /> =Current Course Materials=<br /> <br /> == General Course Information ==<br /> * [https://docs.google.com/a/ihcnt.net/spreadsheet/viewform?formkey=dE5lWno3NEQybjdLOW52OW5aNWpfdnc6MQ First Day Sign In Form]<br /> * [[Franske CNT-2311 Syllabus|Course Syllabus]]<br /> * [[Franske CNT-2311 SP12 Schedule|Spring 2012 Course Schedule]]<br /> * [[Franske CNT-2311 SP12 Labs|Lab List]]<br /> * [[Franske Lab Report Format|Lab Report Format]]<br /> * [[Franske CNT-2311 SP12 Chapter Groups|Spring 2012 Chapter Groups]]<br /> <br /> == Chapter Study Guides ==<br /> Put a link to the study guide you create for your chapter here. &lt;br&gt;<br /> * [[Chapter 2 Study Guide]]<br /> * [[Chapter 3 Study Guide]]<br /> * [[Chapter 4 Study Guide]]<br /> * [[Chapter 5 Study Guide]]<br /> * [[Chapter 6 Study Guide]]<br /> * [[Chapter 7 Study Guide]]<br /> * [[Chapter 8 Study Guide]]<br /> * [[Chapter 9 Study Guide]]<br /> * [[Chapter 10 Study Guide]]<br /> * [[Chapter 14 Study Guide]]<br /> <br /> == Resources ==<br /> * [[Writing Moodle Questions]]<br /> * [[Editing Moodle Questions]]<br /> <br /> === Software ===<br /> * [http://www.virtualbox.org Virtualbox]<br /> ** [[VirtualBox Startup Script]]<br /> <br /> ==== Major Linux Distributions ====<br /> * [http://www.debian.org Debian]<br /> ** [http://www.ubuntu.com Ubuntu]<br /> * [http://www.redhat.com Redhat Enterprise Linux (RHEL)]<br /> ** [http://centos.org CentOS]<br /> ** [http://fedoraproject.org Fedora]<br /> *** Old versions of Fedora are difficult to find on the site the version that the book uses is [http://mirror.rit.edu/fedora/linux/releases/13/Fedora/i386/iso/Fedora-13-i386-DVD.iso Fedora Core 13]<br /> * [http://www.gentoo.org Gentoo]<br /> * [http://www.opensuse.org OpenSUSE (Novell)]<br /> <br /> === General Help ===<br /> ==== Online Linux Tutuorials ====<br /> * [http://www.linux.org/lessons/beginner Beginning Linux from Linux.org]<br /> * [https://help.ubuntu.com/community/PostfixBasicSetupHowto Postfix Basic Setup]<br /> * [http://lartc.org Linux Advanced Routing &amp; Traffic Control (Advanced Networking)]<br /> <br /> === Command Guides ===<br /> * [http://vic.gedris.org/Manual-ShellIntro/1.2/ShellIntro.pdf Inroduction to basic BASH shell commands]<br /> * [http://www.digilife.be/quickreferences/QRC/The%20One%20Page%20Linux%20Manual.pdf The One Page Linux Manual]<br /> <br /> === Specific Topic Help ===<br /> ==== GRUB2 ====<br /> * [https://help.ubuntu.com/community/Grub2 Ubuntu Community Documentation - GRUB2]<br /> * [http://www.dedoimedo.com/computers/grub-2.html GRUB2 Bootloader Full Tutorial]<br /> * [http://ubuntuforums.org/showthread.php?t=1195275 The GRUB2 Guide]<br /> <br /> ==== Runlevels ====<br /> * [http://www.ibm.com/developerworks/linux/library/l-lpic1-v3-101-3/?ca=drs- IBM Learn Linux, 101: Runlevels, shutdown, and reboot]<br /> * [http://www.linux.com/news/enterprise/systems-management/8116-an-introduction-to-services-runlevels-and-rcd-scripts An introduction to services, runlevels, and rc.d scripts]<br /> <br /> ==== Partitioning, Formatting and Mounting====<br /> * [http://tldp.org/HOWTO/Partition/ Linux Partition HOWTO]<br /> * [http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/4/html/Introduction_To_System_Administration/s2-storage-fs-mounting.html RedHat Documentation Mount Points]<br /> * [http://docs.fedoraproject.org/en-US/Fedora/15/html/Installation_Guide/ch-partitions-x86.html Fedora Documentation: An Introduction to Disk Partitions]<br /> <br /> ==== SSH ====<br /> * [http://macnugget.org/projects/publickeys/ David McNett: using ssh public key authentication]<br /> * [https://help.ubuntu.com/community/SSH/OpenSSH/Keys Ubuntu SSH Keys Documentation]<br /> * [http://www.linuxtutorialblog.com/post/ssh-and-scp-howto-tips-tricks Linux Tutorial Blog: SSH and SCP: Howto, tips &amp; tricks]<br /> <br /> ==== Network Configuration ====<br /> * [http://www.debian-administration.org/articles/254 Debian-style Network Configuration] (Ubuntu Server uses the same style)<br /> * [http://docs.fedoraproject.org/en-US/Fedora/15/html/Deployment_Guide/s1-networkscripts-interfaces.html Fedora Nekwork Interface Configuration Files] <br /> <br /> ==== Regular Expressions, Grep and SED ====<br /> * [http://www.zytrax.com/tech/web/regex.htm Regular Expressions - A Simple User Guide]<br /> * [http://linuxreviews.org/beginner/tao_of_regular_expressions Tao of Regular Expressions]<br /> <br /> =Archived Course Materials=<br /> == General Course Information ==<br /> * [[Franske CNT-2311 Labs|Lab List]]<br /> * [[Franske CNT-2311 SU11 Labs|Summer 2011 Lab List]]<br /> <br /> == Chapter Project Notes ==<br /> [[CNT-2311-Chapter 2 Notes]] &lt;br&gt;<br /> [[CNT-2311-Chapter 3 Notes]] &lt;br&gt;<br /> [[CNT-2311-Chapter 4 Notes]] &lt;br&gt;<br /> [[CNT-2311-Chapter 5 Notes]] &lt;br&gt;<br /> [[CNT-2311-Chapter 7 Notes]] &lt;br&gt;<br /> [[CNT-2311-Chapter 8 Notes]] &lt;br&gt;<br /> [[CNT-2311-Chapter 9 Notes]] &lt;br&gt;<br /> [[CNT-2311-Chapter 10 Notes]] &lt;br&gt;<br /> <br /> '''<br /> [http://wiki.ihcnt.net/w/Chapter_21_%26_24 CNT-2311-Chapter 21 &amp; 24 Notes]'''<br /> * [[Linux SSH and Samba Notes]]<br /> * [[Linux Job Management Notes]]<br /> <br /> == Projects ==<br /> <br /> * [[Dual Booting Ubuntu and Windows 7]]<br /> * [[GUID Partiton Table]]<br /> * [[Linux VLAN Trunking]]<br /> * [[Installing Webmin]]<br /> * [[Nat Masquerading and Firewall]]<br /> * [[Control Web Access With Squid]]<br /> * [[Installing MyBB Forum]]<br /> * [[openvpn]]<br /> * [[Zoneminder]]<br /> * [[Understanding Linux Permission Sets]]<br /> * [[Franske CNT-2311 SP10 Commands|Spring 2010 Commands by Session]]<br /> * [[Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage]]<br /> * [[Linux command guide]]<br /> * [[Windows File Sharing and Printer Sharing with SAMBA]]<br /> * [[How to Setup NAT]]<br /> * [[Linux-command-list]]</div>

Powe0122 https://wiki.ihitc.net/mediawiki/index.php?title=Chapter_4_Study_Guide&diff=5192 2012-02-06T23:56:21Z

<p>Powe0122: /* Understand and Create linked files */</p> <hr /> <div>==Understand and Create linked files==<br /> '''What is a linked file?''' A link is a way of matching two or more file names to the same set of file data.<br /> <br /> '''How many ways can a file be linked?''' 2 ways<br /> <br /> '''What are they?''' A symbolic link, or symlic and A hard link.<br /> <br /> '''How are files stored on a file system?'''<br /> <br /> The structural level of a filesystem has three main sections: The superblock, The inode table and data blocks<br /> <br /> '''Superblock :''' Is the section that contains information about the filesystem. Filesystem Type, Size, status, number of inodes.<br /> <br /> '''Inodes Table:''' The collection of inodes for all files and directories on a filesystem. Each file in the Linux system gets its own inode.<br /> '''''Inode'''(The portion of a file that holds information on the file’s attributes, access permissions, where it is located, who owns it, and file type. Each inode contains a unique inode number for identificattion purposes)''<br /> <br /> '''How do you view the inode number? ls -li'''<br /> <br /> '''Data Blocks:''' The data that makes up the content of the file as well as the filename. Blocks are also know as allocation units.<br /> <br /> '''Hard Link Characteristics'''<br /> *In a hard link, two files share the same data<br /> *Hard Link files are direct copies of one another<br /> *Same Size<br /> *They share the same inode and inode number<br /> *The hard link will look and behave the same as the original.<br /> *A file can be hard linked an unlimited number of times if the files reside on the same filesystem.<br /> *Hardlinks can not span across partitions<br /> *Points to a file by its inode<br /> <br /> '''How do you create a Hard Link?'''<br /> To create a hard link you would use the ln (Link) command and specify the existing file to hard link and the target file that will be created.<br /> <br /> '''Symbolic Link or symlic Charateristics'''<br /> *One file is a pointer or shortcut to another file. The files may point to files located on other partitions or other network drives<br /> *Symbolic links do not share the same inode and inode number with their target file<br /> *Different size<br /> *Symbolic links point to another file by its name<br /> *Soft links do not need to reside on the same filesystem<br /> *removing the target file for a symbolic link breaks the link and it will no longer work.<br /> <br /> '''How do you create a symbolic link?'''<br /> To create a symbolic link you would use the ln (Link) command and use –s followed by the target file and the file you want to link.<br /> <br /> ==Identify the default permissions created on files and directories==<br /> New files are given rw-rw-rw- by the system when they are created.<br /> <br /> New directories are given rwxrwxrwx by the system when they are created.</div>

Powe0122 https://wiki.ihitc.net/mediawiki/index.php?title=Chapter_4_Study_Guide&diff=5191 2012-02-06T23:54:19Z

<p>Powe0122: /* Understand and Create linked files */</p> <hr /> <div>==Understand and Create linked files==<br /> '''What is a linked file?''' A link is a way of matching two or more file names to the same set of file data.<br /> <br /> '''How many ways can a file be linked?''' 2 ways<br /> <br /> '''What are they?''' A symbolic link, or symlic and A hard link.<br /> <br /> '''How are files stored on a file system?'''<br /> <br /> The structural level of a filesystem has three main sections: The superblock, The inode table and data blocks<br /> <br /> '''Superblock :''' Is the section that contains information about the filesystem. Filesystem Type, Size, status, number of inodes.<br /> <br /> '''Inodes Table:''' The collection of inodes for all files and directories on a filesystem. Each file in the Linux system gets its own inode.<br /> '''''Inode'''(The portion of a file that holds information on the file’s attributes, access permissions, where it is located, who owns it, and file type. Each inode contains a unique inode number for identificattion purposes)''<br /> <br /> '''How do you view the inode number? ls -li'''<br /> <br /> '''Data Blocks:''' The data that makes up the content of the file as well as the filename. Blocks are also know as allocation units.<br /> '''<br /> Hard Link Characteristics'''<br /> *In a hard link, two files share the same data<br /> *Hard Link files are direct copies of one another<br /> *Same Size<br /> *They share the same inode and inode number<br /> *The hard link will look and behave the same as the original.<br /> *A file can be hard linked an unlimited number of times if the files reside on the same filesystem.<br /> *Hardlinks can not span across partitions<br /> *Points to a file by its inode<br /> <br /> '''How do you create a Hard Link?'''<br /> To create a hard link you would use the ln (Link) command and specify the existing file to hard link and the target file that will be created.<br /> <br /> '''Symbolic Link or symlic Charateristics'''<br /> *One file is a pointer or shortcut to another file. The files may point to files located on other partitions or other network drives<br /> *Symbolic links do not share the same inode and inode number with their target file<br /> *Different size<br /> *Symbolic links point to another file by its name<br /> *Soft links do not need to reside on the same filesystem<br /> *removing the target file for a symbolic link breaks the link and it will no longer work.<br /> <br /> '''How do you create a symbolic link?'''<br /> To create a symbolic link you would use the ln (Link) command and use –s followed by the target file and the file you want to link.<br /> <br /> ==Identify the default permissions created on files and directories==<br /> New files are given rw-rw-rw- by the system when they are created.<br /> <br /> New directories are given rwxrwxrwx by the system when they are created.</div>

Powe0122 https://wiki.ihitc.net/mediawiki/index.php?title=Chapter_4_Study_Guide&diff=5190 2012-02-06T23:53:22Z

<p>Powe0122: /* Understand and Create linked files */</p> <hr /> <div>==Understand and Create linked files==<br /> '''What is a linked file?''' A link is a way of matching two or more file names to the same set of file data.<br /> <br /> '''How many ways can a file be linked?''' 2 ways<br /> <br /> '''What are they?''' A symbolic link, or symlic and A hard link.<br /> <br /> '''How are files stored on a file system?'''<br /> <br /> The structural level of a filesystem has three main sections: The superblock, The inode table and data blocks<br /> <br /> '''Superblock :''' Is the section that contains information about the filesystem. Filesystem Type, Size, status, number of inodes.<br /> <br /> '''Inodes Table:''' The collection of inodes for all files and directories on a filesystem. Each file in the Linux system gets its own inode.<br /> '''''Inode'''(The portion of a file that holds information on the file’s attributes, access permissions, where it is located, who owns it, and file type. Each inode contains a unique inode number for identificattion purposes)'' <br /> '''How do you view the inode number? ls -li'''<br /> <br /> '''Data Blocks:''' The data that makes up the content of the file as well as the filename. Blocks are also know as allocation units.<br /> '''<br /> Hard Link Characteristics'''<br /> *In a hard link, two files share the same data<br /> *Hard Link files are direct copies of one another<br /> *Same Size<br /> *They share the same inode and inode number<br /> *The hard link will look and behave the same as the original.<br /> *A file can be hard linked an unlimited number of times if the files reside on the same filesystem.<br /> *Hardlinks can not span across partitions<br /> *Points to a file by its inode<br /> <br /> '''How do you create a Hard Link?'''<br /> To create a hard link you would use the ln (Link) command and specify the existing file to hard link and the target file that will be created.<br /> <br /> '''Symbolic Link or symlic Charateristics'''<br /> *One file is a pointer or shortcut to another file. The files may point to files located on other partitions or other network drives<br /> *Symbolic links do not share the same inode and inode number with their target file<br /> *Different size<br /> *Symbolic links point to another file by its name<br /> *Soft links do not need to reside on the same filesystem<br /> *removing the target file for a symbolic link breaks the link and it will no longer work.<br /> <br /> '''How do you create a symbolic link?'''<br /> To create a symbolic link you would use the ln (Link) command and use –s followed by the target file and the file you want to link.<br /> <br /> ==Identify the default permissions created on files and directories==<br /> New files are given rw-rw-rw- by the system when they are created.<br /> <br /> New directories are given rwxrwxrwx by the system when they are created.</div>

Powe0122 https://wiki.ihitc.net/mediawiki/index.php?title=Chapter_4_Study_Guide&diff=5189 2012-02-06T23:47:43Z

<p>Powe0122: </p> <hr /> <div>==Understand and Create linked files==<br /> '''What is a linked file?''' A link is a way of matching two or more file names to the same set of file data.<br /> <br /> '''How many ways can a file be linked?''' 2 ways<br /> <br /> '''What are they?''' A symbolic link, or symlic and A hard link.<br /> <br /> '''How are files stored on a file system?'''<br /> <br /> The structural level of a filesystem has three main sections: The superblock, The inode table and data blocks<br /> <br /> '''Superblock :''' Is the section that contains information about the filesystem. Filesystem Type, Size, status, number of inodes.<br /> <br /> '''Inodes Table:''' The collection of inodes ''(The portion of a file that stores information on the file’s attributes, access permissions, location, ownership and file type. Each inode contains a unique inode number for identificattion)'' for all files and directories on a filesystem. Each file in the Linux system gets its own inode.<br /> <br /> '''How do you view the inode number? ls -li'''<br /> <br /> '''Data Blocks:''' The data that makes up the content of the file as well as the filename. Blocks are also know as allocation units.<br /> '''<br /> Hard Link Characteristics'''<br /> *In a hard link, two files share the same data<br /> *Hard Link files are direct copies of one another<br /> *Same Size<br /> *They share the same inode and inode number<br /> *The hard link will look and behave the same as the original.<br /> *A file can be hard linked an unlimited number of times if the files reside on the same filesystem.<br /> *Hardlinks can not span across partitions<br /> *Points to a file by its inode<br /> <br /> '''How do you create a Hard Link?'''<br /> To create a hard link you would use the ln (Link) command and specify the existing file to hard link and the target file that will be created.<br /> [[File:picture1.png]]<br /> <br /> '''Symbolic Link or symlic Charateristics'''<br /> *One file is a pointer or shortcut to another file. These files may point to files located on other partitions or other network drives.<br /> *Symbolic links do not share the same inode and inode number with their target file<br /> *Different size<br /> *Symbolic links point to another file by its name<br /> *Soft links need not reside on the same filesystem<br /> *removing the target file for a symbolic link breaks the link and it will no longer work.<br /> <br /> '''How do you create a symbolic link?'''<br /> To create a symbolic link you would use the ln (Link) command and use –s followed by the target file and the file you want to link.<br /> <br /> ==Identify the default permissions created on files and directories==<br /> New files are given rw-rw-rw- by the system when they are created.<br /> <br /> New directories are given rwxrwxrwx by the system when they are created.</div>

Powe0122 https://wiki.ihitc.net/mediawiki/index.php?title=Chapter_4_Study_Guide&diff=5188 2012-02-06T23:41:56Z

<p>Powe0122: /* Understand and Create linked files */</p> <hr /> <div>==Understand and Create linked files==<br /> '''What is a linked file?''' A link is a way of matching two or more file names to the same set of file data.<br /> <br /> '''How many ways can a file be linked?''' 2 ways<br /> <br /> '''What are they?''' A symbolic link, or symlic and A hard link.<br /> <br /> '''How are files stored on a file system?'''<br /> <br /> The structural level of a filesystem has three main sections: The superblock, The inode table and data blocks<br /> <br /> '''Superblock :''' Is the section that contains information about the filesystem. Filesystem Type, Size, status, number of inodes.<br /> <br /> '''Inodes Table:''' The collection of inodes ''(The portion of a file that stores information on the file’s attributes, access permissions, location, ownership and file type. Each inode contains a unique inode number for identificattion)'' for all files and directories on a filesystem. Each file in the Linux system gets its own inode.<br /> <br /> '''How do you view the inode number? ls -li'''<br /> <br /> '''Data Blocks:''' The data that makes up the content of the file as well as the filename. Blocks are also know as allocation units.<br /> '''<br /> Hard Link Characteristics'''<br /> *In a hard link, two files share the same data<br /> *Hard Link files are direct copies of one another<br /> *Same Size<br /> *They share the same inode and inode number<br /> *The hard link will look and behave the same as the original.<br /> *A file can be hard linked an unlimited number of times if the files reside on the same filesystem.<br /> *Hardlinks can not span across partitions<br /> *Points to a file by its inode<br /> <br /> '''How do you create a Hard Link?'''<br /> To create a hard link you would use the ln (Link) command and specify the existing file to hard link and the target file that will be created.<br /> <br /> '''Symbolic Link or symlic Charateristics'''<br /> *One file is a pointer or shortcut to another file. These files may point to files located on other partitions or other network drives.<br /> *Symbolic links do not share the same inode and inode number with their target file<br /> *Different size<br /> *Symbolic links point to another file by its name<br /> *Soft links need not reside on the same filesystem<br /> *removing the target file for a symbolic link breaks the link and it will no longer work.<br /> <br /> '''How do you create a symbolic link?'''<br /> To create a symbolic link you would use the ln (Link) command and use –s followed by the target file and the file you want to link.<br /> <br /> ==Identify the default permissions created on files and directories==<br /> New files are given rw-rw-rw- by the system when they are created.<br /> <br /> New directories are given rwxrwxrwx by the system when they are created.</div>

Powe0122 https://wiki.ihitc.net/mediawiki/index.php?title=Chapter_4_Study_Guide&diff=5187 2012-02-06T23:40:47Z

<p>Powe0122: </p> <hr /> <div>==Understand and Create linked files==<br /> '''What is a linked file?''' A link is a way of matching two or more file names to the same set of file data.<br /> <br /> '''How many ways can a file be linked?''' 2 ways<br /> <br /> '''What are they?''' A symbolic link, or symlic and A hard link.<br /> <br /> '''How are files stored on a file system?'''<br /> <br /> The structural level of a filesystem has three main sections: The superblock, The inode table and data blocks<br /> <br /> '''Superblock :''' Is the section that contains information about the filesystem. Filesystem Type, Size, status, number of inodes.<br /> <br /> '''Inodes Table:''' The collection of inodes ''(The portion of a file that stores information on the file’s attributes, access permissions, location, ownership and file type. Each inode contains a unique inode number for identificattion)'' for all files and directories on a filesystem. Each file in the Linux system gets its own inode.<br /> <br /> '''How do you view the inode number? ls -li'''<br /> '''Data Blocks:''' The data that makes up the content of the file as well as the filename. Blocks are also know as allocation units.<br /> '''<br /> Hard Link Characteristics'''<br /> *In a hard link, two files share the same data<br /> *Hard Link files are direct copies of one another<br /> *Same Size<br /> *They share the same inode and inode number<br /> *The hard link will look and behave the same as the original.<br /> *A file can be hard linked an unlimited number of times if the files reside on the same filesystem.<br /> *Hardlinks can not span across partitions<br /> *Points to a file by its inode<br /> <br /> '''How do you create a Hard Link?'''<br /> To create a hard link you would use the ln (Link) command and specify the existing file to hard link and the target file that will be created.<br /> <br /> '''Symbolic Link or symlic Charateristics'''<br /> *One file is a pointer or shortcut to another file. These files may point to files located on other partitions or other network drives.<br /> *Symbolic links do not share the same inode and inode number with their target file<br /> *Different size<br /> *Symbolic links point to another file by its name<br /> *Soft links need not reside on the same filesystem<br /> *removing the target file for a symbolic link breaks the link and it will no longer work.<br /> <br /> '''How do you create a symbolic link?'''<br /> To create a symbolic link you would use the ln (Link) command and use –s followed by the target file and the file you want to link. <br /> <br /> ==Identify the default permissions created on files and directories==<br /> New files are given rw-rw-rw- by the system when they are created.<br /> <br /> New directories are given rwxrwxrwx by the system when they are created.</div>

Powe0122 https://wiki.ihitc.net/mediawiki/index.php?title=Chapter_4_Study_Guide&diff=5186 2012-02-06T23:36:17Z

<p>Powe0122: </p> <hr /> <div>==Understand and Create linked files==<br /> '''What is a linked file?''' A link is a way of matching two or more file names to the same set of file data.<br /> <br /> '''How many ways can a file be linked?''' 2 ways<br /> <br /> '''What are they?''' A symbolic link, or symlic and A hard link.<br /> <br /> '''How are files stored on a file system?'''<br /> <br /> The structural level of a filesystem has three main sections: The superblock, The inode table and data blocks<br /> <br /> '''Superblock :''' Is the section that contains information about the filesystem. Filesystem Type, Size, status, number of inodes.<br /> <br /> '''Inodes Table:''' The collection of inodes ''(The portion of a file that stores information on the file’s attributes, access permissions, location, ownership and file type. Each inode contains a unique inode number for identificattion)'' for all files and directories on a filesystem. Each file in the Linux system gets its own inode.<br /> <br /> '''Data Blocks:''' The data that makes up the content of the file as well as the filename. Blocks are also know as allocation units.</div>

Powe0122 https://wiki.ihitc.net/mediawiki/index.php?title=Chapter_4_Study_Guide&diff=5185 2012-02-06T23:29:35Z

<p>Powe0122: </p> <hr /> <div>==Understand and Create linked files==</div>

Powe0122 https://wiki.ihitc.net/mediawiki/index.php?title=Franske_CNT-2311&diff=5161 2012-02-03T01:49:50Z

<p>Powe0122: /* Chapter Study Guides */</p> <hr /> <div>This is the homepage for the CNT-2311 classes taught by Dr. Ben Franske.<br /> <br /> =Current Course Materials=<br /> <br /> == General Course Information ==<br /> * [https://docs.google.com/a/ihcnt.net/spreadsheet/viewform?formkey=dE5lWno3NEQybjdLOW52OW5aNWpfdnc6MQ First Day Sign In Form]<br /> * [[Franske CNT-2311 Syllabus|Course Syllabus]]<br /> * [[Franske CNT-2311 SP12 Schedule|Spring 2012 Course Schedule]]<br /> * [[Franske CNT-2311 SP12 Labs|Lab List]]<br /> * [[Franske Lab Report Format|Lab Report Format]]<br /> * [[Franske CNT-2311 SP12 Chapter Groups|Spring 2012 Chapter Groups]]<br /> <br /> == Chapter Study Guides ==<br /> Put a link to the study guide you create for your chapter here. &lt;br&gt;<br /> [[Chapter 2 Study Guide]]<br /> <br /> [[Chapter 3 Study Guide]]<br /> <br /> [[Chapter 4 Study Guide]]<br /> <br /> == Resources ==<br /> * [[Writing Moodle Questions]]<br /> * [[Editing Moodle Questions]]<br /> <br /> === Software ===<br /> * [http://www.virtualbox.org Virtualbox]<br /> ** [[VirtualBox Startup Script]]<br /> <br /> ==== Major Linux Distributions ====<br /> * [http://www.debian.org Debian]<br /> ** [http://www.ubuntu.com Ubuntu]<br /> * [http://www.redhat.com Redhat Enterprise Linux (RHEL)]<br /> ** [http://centos.org CentOS]<br /> ** [http://fedoraproject.org Fedora]<br /> *** Old versions of Fedora are difficult to find on the site the version that the book uses is [http://mirror.rit.edu/fedora/linux/releases/13/Fedora/i386/iso/Fedora-13-i386-DVD.iso Fedora Core 13]<br /> * [http://www.gentoo.org Gentoo]<br /> * [http://www.opensuse.org OpenSUSE (Novell)]<br /> <br /> === General Help ===<br /> ==== Online Linux Tutuorials ====<br /> * [http://www.linux.org/lessons/beginner Beginning Linux from Linux.org]<br /> * [https://help.ubuntu.com/community/PostfixBasicSetupHowto Postfix Basic Setup]<br /> * [http://lartc.org Linux Advanced Routing &amp; Traffic Control (Advanced Networking)]<br /> <br /> === Command Guides ===<br /> * [http://vic.gedris.org/Manual-ShellIntro/1.2/ShellIntro.pdf Inroduction to basic BASH shell commands]<br /> * [http://www.digilife.be/quickreferences/QRC/The%20One%20Page%20Linux%20Manual.pdf The One Page Linux Manual]<br /> <br /> === Specific Topic Help ===<br /> ==== GRUB2 ====<br /> * [https://help.ubuntu.com/community/Grub2 Ubuntu Community Documentation - GRUB2]<br /> * [http://www.dedoimedo.com/computers/grub-2.html GRUB2 Bootloader Full Tutorial]<br /> * [http://ubuntuforums.org/showthread.php?t=1195275 The GRUB2 Guide]<br /> <br /> ==== Runlevels ====<br /> * [http://www.ibm.com/developerworks/linux/library/l-lpic1-v3-101-3/?ca=drs- IBM Learn Linux, 101: Runlevels, shutdown, and reboot]<br /> * [http://www.linux.com/news/enterprise/systems-management/8116-an-introduction-to-services-runlevels-and-rcd-scripts An introduction to services, runlevels, and rc.d scripts]<br /> <br /> ==== Partitioning, Formatting and Mounting====<br /> * [http://tldp.org/HOWTO/Partition/ Linux Partition HOWTO]<br /> * [http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/4/html/Introduction_To_System_Administration/s2-storage-fs-mounting.html RedHat Documentation Mount Points]<br /> * [http://docs.fedoraproject.org/en-US/Fedora/15/html/Installation_Guide/ch-partitions-x86.html Fedora Documentation: An Introduction to Disk Partitions]<br /> <br /> ==== SSH ====<br /> * [http://macnugget.org/projects/publickeys/ David McNett: using ssh public key authentication]<br /> * [https://help.ubuntu.com/community/SSH/OpenSSH/Keys Ubuntu SSH Keys Documentation]<br /> * [http://www.linuxtutorialblog.com/post/ssh-and-scp-howto-tips-tricks Linux Tutorial Blog: SSH and SCP: Howto, tips &amp; tricks]<br /> <br /> ==== Network Configuration ====<br /> * [http://www.debian-administration.org/articles/254 Debian-style Network Configuration] (Ubuntu Server uses the same style)<br /> * [http://docs.fedoraproject.org/en-US/Fedora/15/html/Deployment_Guide/s1-networkscripts-interfaces.html Fedora Nekwork Interface Configuration Files] <br /> <br /> ==== Regular Expressions, Grep and SED ====<br /> * [http://www.zytrax.com/tech/web/regex.htm Regular Expressions - A Simple User Guide]<br /> * [http://linuxreviews.org/beginner/tao_of_regular_expressions Tao of Regular Expressions]<br /> <br /> =Archived Course Materials=<br /> == General Course Information ==<br /> * [[Franske CNT-2311 Labs|Lab List]]<br /> * [[Franske CNT-2311 SU11 Labs|Summer 2011 Lab List]]<br /> <br /> == Chapter Project Notes ==<br /> [[CNT-2311-Chapter 2 Notes]] &lt;br&gt;<br /> [[CNT-2311-Chapter 3 Notes]] &lt;br&gt;<br /> [[CNT-2311-Chapter 4 Notes]] &lt;br&gt;<br /> [[CNT-2311-Chapter 5 Notes]] &lt;br&gt;<br /> [[CNT-2311-Chapter 7 Notes]] &lt;br&gt;<br /> [[CNT-2311-Chapter 8 Notes]] &lt;br&gt;<br /> [[CNT-2311-Chapter 9 Notes]] &lt;br&gt;<br /> [[CNT-2311-Chapter 10 Notes]] &lt;br&gt;<br /> <br /> '''<br /> [http://wiki.ihcnt.net/w/Chapter_21_%26_24 CNT-2311-Chapter 21 &amp; 24 Notes]'''<br /> * [[Linux SSH and Samba Notes]]<br /> * [[Linux Job Management Notes]]<br /> <br /> == Projects ==<br /> <br /> * [[Dual Booting Ubuntu and Windows 7]]<br /> * [[GUID Partiton Table]]<br /> * [[Linux VLAN Trunking]]<br /> * [[Installing Webmin]]<br /> * [[Nat Masquerading and Firewall]]<br /> * [[Control Web Access With Squid]]<br /> * [[Installing MyBB Forum]]<br /> * [[openvpn]]<br /> * [[Zoneminder]]<br /> * [[Understanding Linux Permission Sets]]<br /> * [[Franske CNT-2311 SP10 Commands|Spring 2010 Commands by Session]]<br /> * [[Converting VMWare .vmdk To VirtualBox .vdi Using Qemu+ and VBoxManage]]<br /> * [[Linux command guide]]<br /> * [[Windows File Sharing and Printer Sharing with SAMBA]]<br /> * [[How to Setup NAT]]<br /> * [[Linux-command-list]]</div>

Powe0122 https://wiki.ihitc.net/mediawiki/index.php?title=Chapter_4_Study_Guide&diff=5160 2012-02-03T01:45:34Z

<p>Powe0122: Created page with &quot;coming soon&quot;</p> <hr /> <div>coming soon</div>

Powe0122 https://wiki.ihitc.net/mediawiki/index.php?title=Franske_CNT-2311_SP12_Chapter_Groups&diff=5157 2012-02-03T01:39:05Z

<p>Powe0122: /* Chapter 14 */</p> <hr /> <div>=Chapter 1=<br /> * N/A - Read on Your Own<br /> =Chapter 2=<br /> *Clay Wilson<br /> *Mike Garin<br /> *Rob Klaers<br /> *Todd Baily<br /> =Chapter 3=<br /> *Randy Oye<br /> *Tracy Ryder<br /> *Dave Litke<br /> *Dan Madigan<br /> =Chapter 4=<br /> *Andrew Powell<br /> *Jesse Bruhn<br /> *Sean Bencker<br /> *Scott Pomerleau<br /> *Laprice Ali<br /> =Chapter 5=<br /> *Thu Nguyen<br /> *Tyler Gray<br /> *Jason Backley<br /> *Naut Obermuelle<br /> =Chapter 6=<br /> *Kevin<br /> *George<br /> *Gill<br /> *Ryan<br /> =Chapter 7=<br /> *Jason Backley<br /> *Tyler Gray<br /> *Matt Obermueller<br /> *Thu Nguyen<br /> BAM!!!!!<br /> <br /> =Chapter 8=<br /> *<br /> *<br /> *<br /> <br /> =Chapter 9=<br /> *Randy Oye<br /> *Dave Litke<br /> *Tracy Stoltz<br /> <br /> =Chapter 10=<br /> *<br /> *<br /> *<br /> =Chapter 11=<br /> *<br /> *<br /> *<br /> =Chapter 12=<br /> * Ben Franske<br /> =Chapter 13=<br /> *<br /> *<br /> *<br /> =Chapter 14=<br /> * Andrew Powell<br /> * Jesse<br /> * Scott</div>

Powe0122 https://wiki.ihitc.net/mediawiki/index.php?title=Franske_CNT-2311_SP12_Chapter_Groups&diff=5156 2012-02-03T01:35:22Z

<p>Powe0122: /* Chapter 14 */</p> <hr /> <div>=Chapter 1=<br /> * N/A - Read on Your Own<br /> =Chapter 2=<br /> *Clay Wilson<br /> *Mike Garin<br /> *Rob Klaers<br /> *Todd Baily<br /> =Chapter 3=<br /> *Randy Oye<br /> *Tracy Ryder<br /> *Dave Litke<br /> *Dan Madigan<br /> =Chapter 4=<br /> *Andrew Powell<br /> *Jesse Bruhn<br /> *Sean Bencker<br /> *Scott Pomerleau<br /> *Laprice Ali<br /> =Chapter 5=<br /> *Thu Nguyen<br /> *Tyler Gray<br /> *Jason Backley<br /> *Naut Obermuelle<br /> =Chapter 6=<br /> *Kevin<br /> *George<br /> *Gill<br /> *Ryan<br /> =Chapter 7=<br /> *Jason Backley<br /> *Tyler Gray<br /> *Matt Obermueller<br /> *Thu Nguyen<br /> BAM!!!!!<br /> <br /> =Chapter 8=<br /> *<br /> *<br /> *<br /> <br /> =Chapter 9=<br /> *Randy Oye<br /> *Dave Litke<br /> *Tracy Stoltz<br /> <br /> =Chapter 10=<br /> *<br /> *<br /> *<br /> =Chapter 11=<br /> *<br /> *<br /> *<br /> =Chapter 12=<br /> * Ben Franske<br /> =Chapter 13=<br /> *<br /> *<br /> *<br /> =Chapter 14=<br /> * Andrew Powell<br /> * Jesse<br /> * Scott<br /> * Sean<br /> * LaPrice</div>

Powe0122 https://wiki.ihitc.net/mediawiki/index.php?title=Franske_CNT-2311_SP12_Chapter_Groups&diff=5155 2012-02-03T01:07:36Z

<p>Powe0122: /* Chapter 14 */</p> <hr /> <div>=Chapter 1=<br /> * N/A - Read on Your Own<br /> =Chapter 2=<br /> *Clay Wilson<br /> *Mike Garin<br /> *Rob Klaers<br /> *Todd Baily<br /> =Chapter 3=<br /> *Randy Oye<br /> *Tracy Ryder<br /> *Dave Litke<br /> *Dan Madigan<br /> =Chapter 4=<br /> *Andrew Powell<br /> *Jesse Bruhn<br /> *Sean Bencker<br /> *Scott Pomerleau<br /> *Laprice Ali<br /> =Chapter 5=<br /> *Thu Nguyen<br /> *Tyler Gray<br /> *Jason Backley<br /> *Naut Obermuelle<br /> =Chapter 6=<br /> *Kevin<br /> *George<br /> *Gill<br /> *Ryan<br /> =Chapter 7=<br /> *Jason Backley<br /> *Tyler Gray<br /> *Matt Obermueller<br /> *Thu Nguyen<br /> BAM!!!!!<br /> <br /> =Chapter 8=<br /> *<br /> *<br /> *<br /> <br /> =Chapter 9=<br /> *Randy Oye<br /> *Dave Litke<br /> *Tracy Stoltz<br /> <br /> =Chapter 10=<br /> *<br /> *<br /> *<br /> =Chapter 11=<br /> *<br /> *<br /> *<br /> =Chapter 12=<br /> * Ben Franske<br /> =Chapter 13=<br /> *<br /> *<br /> *<br /> =Chapter 14=<br /> * Andrew Powell<br /> *<br /> *</div>

Powe0122