
Torubleshooting commands????
news:7e3a95e5.0305162219.24164d1@posting.google.com
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 http://www.geek-girl.com/Unixhelp/ 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.
tony
--
use hotmail com for any email replies
-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 80,000 Newsgroups - 16 Different Servers! =-----