Solving a Problem


Following is a list of steps that can help you solve a problem without asking someone for help. Depending on your understanding of and experience with the hardware and software involved, these steps may lead to a solution.

1.

Red Hat Linux comes with extensive documentation. Read the documentation on the specific hardware or software you are having a problem with. If it is a GNU product, use info; otherwise, use man to find local information. Also look in /usr/share/doc for documentation on specific tools. For more information refer to "Getting the Facts: Where to Find Documentation" on page 102.

2.

When the problem involves some type of error or other message, use a search engine, such as Google (www.google.com/linux) or Google Groups (groups.google.com), to look up the message on the Internet. If the message is long, pick a unique part of the message to search for; 10 to 20 characters should be enough. Enclose the search string within double quotation marks.

3.

Check whether the Linux Documentation Project (www.tldp.org) has a HOWTO or mini-HOWTO on the subject in question. Search on keywords that relate directly to the product and problem. Read the FAQs.

4.

See Table B-1 for other sources of documentation.

5.

Use Google or Google Groups to search on keywords that relate directly to the product and problem.

6.

When all else fails (or perhaps before you try anything else), examine the system logs in /var/log. Running as Superuser, first look at the end of the messages file using the following command:

# tail -20 /var/log/messages


If messages contains nothing useful, run the following command. It displays the names of the log files in chronological order, with the most recently modified files appearing at the bottom of the list:

$ ls -ltr /var/log


If the problem involves a network connection, review the secure log file on the local and remote systems. Also look at messages on the remote system.

7.

The /var/spool directory contains subdirectories with useful information: cups holds the print queues, mail holds the user's mail files, and so on.

If you are unable to solve a problem yourself, a thoughtful question to an appropriate newsgroup (page 981) or mailing list (page 981) can elicit useful information.

When you send or post a question, make sure you describe the problem and identify the local system carefully. Include the version numbers of Red Hat Linux and any software packages that relate to the problem. Describe the hardware, if appropriate. For a fee, Red Hat provides many types of support.

The author's home page (www.sobell.com) contains corrections to this book, answers to selected chapter exercises, and pointers to other Linux sites.




A Practical Guide to Red Hat Linux
A Practical Guide to Red HatВ® LinuxВ®: Fedoraв„ў Core and Red Hat Enterprise Linux (3rd Edition)
ISBN: 0132280272
EAN: 2147483647
Year: 2006
Pages: 383

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net