Sakshi Student's Community Forum! Click here to Register free


Thursday, January 7, 2010

Red Hat Publications Ebooks

RH142 Linux Troubleshooting Techniques and Tools

Course Description:

Troubleshooting is both an art and a science, an instinct (typically informed by experience) and a technique. In RH142 Linux Troubleshooting Techniques and Tools, participants will learn techniques for troubleshooting a Linux system and will learn to use a variety of troubleshooting tools available on Red Hat Enterprise Linux.RH142 Linux Troubleshooting Techniques and Tools is a 4 day heavily lab-oriented class designed to help participants learn (or improve) their troubleshooting skills using tools available in Red Hat Enterprise Linux. Labs will offer a range of problems from RHCT level and up to allow participants to extend their knowledge and techniques.Participants will have the opportunity to debug live systems, exercising their new troubleshooting skills on a working system so that they can start to (or continue to) develop troubleshooting experience.For a complete outline of the material taught in this course, see the Outline for RH142 Red Hat Enterprise Linux Troubleshooting course.

Goal:

A Red Hat Enterprise Linux system administrator who can identify, diagnose, and resolve problems on a Red Hat Enterprise Linux system, and who can take preventative action to avoid problems.

Audience:

Linux system administrators who understand how to install and configure a Red Hat Enterprise Linux system and who wish to deepen their understanding of troubleshooting on Linux.Prerequisites:* Has successfully completed RH131 or RH133; or:* Holds a current RHCT certification; or:* Has equivalent system administration knowledge under Red Hat Enterprise Linux. This knowledge includes: installation, service management (using service and chkconfig, for example), basic system monitoring (using ps and top, and perhaps meminfo and the /proc filesystem), filesystem management (using fdisk and mkfs), and basic troubleshooting (including managing log files and perhaps the use of hardware probing tools such as ethtool and lspci).

No comments:

Post a Comment