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.
echo ' Script A '
echo "You want to do this (y/n) ?"
# locking mechanism, prevents the script running concurrenty, and outputs the current status
if [ -d /tmp/clone.lock ]; then
tail -f $lock_file
echo "WARNING locked process - currently it is doing...." >> $lock_file
if [ "$answer" == "y" ]; then
echo `date '+%T %d-%m-%Y'`
echo "Step 1 completed" | tee -a $lock_file
echo "Step 2 completed" | tee -a $lock_file
echo "Step 3 completed" | tee -a $lock_file
echo "Step 4 completed" | tee -a $lock_file
echo `date '+%T %d-%m-%Y'`
echo -e "Not doing this"
# this should kill tail -f on the $lock_file, which only get's called if the script is aready running
/sbin/fuser -k -s $lock_file &> /dev/null
rm -r /tmp/clone.lock
Almost, the problem that I have is when you call the script...
* it does kill tail -f (awesome)
* it reports back to the terminal (i.e. the other two screens, that tail -f has been killed by (insert script name here) and by line....xx (not good)
./scriptA: line 14: 25514 Killed tail -f $lock_file
I'm hoping there's a way to have that NOT been returned to the terminal.
you can't get it NOT to output the "Killed" to the terminal
I know I tried all my bash foo, and nothing. I guess it stands to reason, imagine if your looking at a file with tail -f and all of a sudden you're back a shell prompt. No explanation and the like, I'd be thinking WTF?