[SOLVED] shell shell to execute commands for pgrep
ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
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.
pgrep qemu will return the pids of the processes
for p in `pgrep qemu` will construct a loop and p will be set to every pid one by one. see the man page of bash, how it works
$p is the value of the variable p - inside the loop.
If you really want to say thanks, press Yes on the bottom right corner....
Except that values of variables within the loop are lost after it ends. It would rather be best to use named pipes with bash instead:
Absolutely correct. Actually, I went with the piped form because I wasn't sure which shell the OP was using, and because the command inside the loop was stand-alone, so the variable didn't appear to be needed elsewhere. I was feeling a bit lazy and didn't feel like posting both versions, so I chose to stick with the portable one.