|
|
Sponsored Content
Top Forums
UNIX for Dummies Questions & Answers
BASH Pipe question
Post 302355500 by mgrahamnz on Tuesday 22nd of September 2009 10:31:40 PM
09-22-2009
Thanks very much - that's exactly what I wanted to do.
I have subsequently worked out I can achieve the same result with 'killall -9 -ir evol*' which is briefer. However, your answer addresses the underlying question I had of how to get a the listed (piped) results to be loped through.
Thanks very much!!!
I have subsequently worked out I can achieve the same result with 'killall -9 -ir evol*' which is briefer. However, your answer addresses the underlying question I had of how to get a the listed (piped) results to be loped through.
Thanks very much!!!
|
|
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
My question is can you use the pipe more than one time in the same command line? By the way I am new to UNIX. Thanks in advanced! (3 Replies)
Discussion started by: elkoreanopr
3 Replies
2. Shell Programming and Scripting
how do you pipe the results to next statement as argument?
somecommand | grep $result somefile
how do you reference $result with?? (12 Replies)
Discussion started by: convenientstore
12 Replies
3. Programming
Hello everybody.I want to make clear that i am not going to ask from anybody to build my asignement but i have a big problem. I can't seem to find anywhere ONE good example on C about what i am trying to do:wall:.I think it is simple. All i ask is one example, even a link is fine.
So, i want to... (1 Reply)
Discussion started by: Cuervo
1 Replies
4. Shell Programming and Scripting
Hello,
I am trying to make a bash script that can pull data from a file and then change one part of said data.
I want to search by username and pull the full line. That way there is a way to replace just one part of that line then return it back to the file.
My Data is stored like:
... (1 Reply)
Discussion started by: serverfull
1 Replies
5. Shell Programming and Scripting
Guy's,
I need help with creating a pipe, I found this code online but not exactly sure what different parts are doing.
Will someone be able to help me with explaining what code is doing?
Also what I want is to have everything the same directory. Meaning I am working in directory:
I want... (5 Replies)
Discussion started by: INHF
5 Replies
6. Shell Programming and Scripting
Hi,
I'm trying to write a script that checks gvfs to see if a mount exists so I can run it from network-manager's status hooks. I thought I'd pipe the output of gvfs-mount -l to grep for the particular mounts I care about. When I do this in a bash script:
cmnd="gvfs-mount -l | grep -i... (4 Replies)
Discussion started by: kcstrom
4 Replies
7. UNIX for Dummies Questions & Answers
Hello.
I want to get all modules which are loaded and which name are exactly 2 characters long and not more than 2 characters and begin with "nv"
lsmod | (e)grep '^nv????????????
I want to get all modules which are loaded and which name begin with "nv" and are 2 to 7 characters long
... (1 Reply)
Discussion started by: jcdole
1 Replies
8. Shell Programming and Scripting
Hi all,
Am trying to convert a script from ksh to bash :wall:. One of the sub is something like below:
#!/bin/bash
declare -a array01
step_01_test()
{
local count=0
ps -ef | grep watch | grep -v grep | awk '{ print $8 }' | while read line
do
let count=${count}+1
... (1 Reply)
Discussion started by: newbie_01
1 Replies
9. UNIX for Advanced & Expert Users
Heays
So i have that script to which i'd like to pipe (rather than just regular arguments) some data from another virtual output command.
Simplified:
echo * | script.sh
When i know how many args i expect, i can handle this simple by:
&& \
read ONE TWO && \
set ONE TWO
echo "$1 : $2... (7 Replies)
Discussion started by: sea
7 Replies
10. Shell Programming and Scripting
What is the proper way to run two bash loops in the same command? The two below loops run separately, the problem is when I pipe them I get an error that the file used for the second loop does not exist. I am not sure how to wait for the first loop to complete and then start the second. Thank... (10 Replies)
Discussion started by: cmccabe
10 Replies
LEARN ABOUT OSF1
killall
killall(8) System Manager's Manual killall(8) NAME
killall - Terminates all processes started by the user, except the calling process SYNOPSIS
/usr/sbin/killall [- | [-]signal_name | -signal_number] /usr/sbin/killall -l FLAGS
The hyphen character (without an argument) sends a SIGTERM signal initially and then sends a SIGKILL signal to all processes that survive for 30 seconds after receipt of the first signal. This gives processes that catch the SIGTERM signal an opportunity to clean up. A signal name, optionally preceded by a hyphen, sends the specified signal to processes. The hyphen character (with a signal number argument) sends the specified signal, either a name, stripped of the SIG prefix (such as KILL), or a number (such as 9). For information about signal names and numbers, see the signal() system call. In the System V habitat, the optional signal number does not have to be preceded with a hyphen (-). Lists signal names in numerical order (as given in the /usr/include/signal.h file), stripped of the common SIG prefix. DESCRIPTION
This command provides a convenient means of killing all processes created by the shell that you control. When started by the superuser, the killall command kills all processes that can be terminated, except those processes that started it, the kernel processes, and processes 0 and 1 (init). Security Configuration This command is modified in all security configurations of the system. EXAMPLES
To stop all background processes that have started, enter: killall This sends all background processes signal 9 (the kill signal, also called SIGKILL). To stop all background processes, giving them a chance to clean up, enter: killall - This sends signal 15 (SIGTERM), waits 30 seconds, and then sends signal 9 (SIGKILL). To send a specific signal to the background processes, enter: killall -2 This sends signal 2 (SIGINT) to the background processes. To list the signal names in numerical order, stripped of the SIG prefix, enter: killall -l This displays a list of signals, which may vary from system to system. FILES
Specifies the command path RELATED INFORMATION
Calls: kill(2), sigaction(2), signal(2) delim off killall(8)