It is currently Thu, 08 Jun 2023 12:51:24 GMT

Author Message
 Torubleshooting commands????
I am writing a small manual for our department, basically for all of
us who are new to Linux?

As part of this manual, I would like to inculde a list of commands
that one would run to troubleshoot the LINUX machine?

Since I am also new to this? I would like some suggestions on the list
of commands I should include?

I am looking for commands which would run as a normal user and also
commands that would only run as root?

 Wed, 02 Nov 2005 14:19:58 GMT   
 Torubleshooting commands????

Why would you undertake such a task if you are new and lacking in knowledge
about such things? You have so much yet to learn about the system itself,
much more any troubleshooting of it, that I'm afraid to suggest that you
don't know what you've gotten yourself into.

Troubleshooting is an art as much as a science, and involves knowing how
things *should* be, as well as a firm grasp of how they *are*. The art comes
in deciding what tactics will be useful to gather evidence (which I gather
is your request here), and far more in interpreting that gathered evidence
to come to a tentative conclusion of the nature of the problem.

How one explores a problem has everything to do with the nature of the
problem, but how one interprets the results is even more important. You can
make a list of diagnostic commands such as ls, find, df, du, groups, strace,
top, echo, traceroute, ping, netstat, umask,and many, many others, but the
data returned from any of them will only have utility in certain situations.

If a person is new to *nix, probably the best diagnostic command they can
learn, and learn well, is "man". Then they should spend as much time as
possible at a site such as and get to
know it inside-out and upside-down.

Then they'll be able to understand the way things *should* be, and they'll
(hopefully) be able to see their own contribution to their problems rather
than blaming everything on the machine.

Most problems are between the chair and the keyboard.


use hotmail com for any email replies

-----= Posted via Newsfeeds.Com, Uncensored Usenet News =----- - The #1 Newsgroup Service in the World!
-----==  Over 80,000 Newsgroups - 16 Different Servers! =-----

 Wed, 02 Nov 2005 17:11:09 GMT   
 Torubleshooting commands????

I agree.  Its like saying you've agreed to write a manual for
troubleshooting cars and what tools do you need to fix and diagnose them.
Each response will warrant its own tool or set of tools.

While most would love to help you with this endevour, the best is to use
"man" as mentioned above.  Also, google searches will help enormously.  My
strongest suggestion is to purchase a few Linux books from a store and use
online resources vs compiling a guide that may prove to be useless.

ken k

 Sat, 05 Nov 2005 00:39:19 GMT   
   [ 3 post ] 

Similar Threads

1. Command editing inside a Unix command

2. command line commands

3. From field incorrect when using Mail command from Command Line

4. Translating ARP commands from linux syntax to dos command prompt

5. man pages for C commands (GCC commands)

6. Command for showing command time records

7. PS command - view initial command ?

8. command(s) that emulate Solaris prtdiag command

9. Command or piped commands to show directory size...

10. Date stamping commands in the shell command history file

Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by ST Software