Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I want to write a script which will be configuring and making a series of programs. I would like to have some form of error checking. It doesn't have to be that sophistocated. Just something that will stop the script on errors.
How can I do this?
typically in BASH, and mind you im still relatively new to BASH myself, if there is an error in the script it will crash at that point.
you can always use test statements to verify before you continue, that is one form of error checking. what exactly are you looking for and what have you written so far? please place your script in "code" flags. you get this by going to advance posting options or by placing code /code inside of 
All Unix processes are automatically given 3 i/o channels on creation/startup
chan 0 = stdin
chan 1 = stdout
chan 2 = stderr
So we're directing '1' (stdout) to logfile and directing 2 (stderr) to the same address (&) as 1 ie the logfile.
Its possible to have separate output and err files, but its tricky to match them up afterwards, so usually you put them both to the same file.