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.
is a very long command and without my script it always output something to console, but in my script it starts, for the long time nothing outputs and after a while outputs a lof of data.
Is any way in my script to output data as soon as it is available, but not all data in the same time after long waiting?
The point of my post is one should know the system before deciding to re-invent the wheel. Conflicts will obviously always remain an issue that requires human intervention, mirror fails aren't fatal unless none of the mirrors work, timeouts aren't interesting unless the updates won't be fetched from that or another mirror. If verbose or error reporting is required the OP should look at yum-updatesd first.
Because that doesn't record the input. What answers to prompts were done?
Using redirection works, but assuming all yes responses is not necessarily complete.
The other advantage script has is that it will make a complete log of the session - so anything done to correct/alter the situation during install (such as doing a "yum clean", killing any stuck processes/locks may also be significant.