Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Problems passing strings within an array
Top Forums UNIX for Dummies Questions & Answers Problems passing strings within an array Post 302780055 by hungryd on Wednesday 13th of March 2013 05:19:18 PM
Old 03-13-2013
Display Problems passing strings within an array
i have a list of apps that i need to forcequit and, from time to time, that list changes. perfect excuse to manage a single array! however, my strings with spaces aren't passing as i'd like them to. here's the simple script:

Code:
#!/bin/sh

#-----Array
apps=( firefox-bin firefox JavaApplicationStub groupwise "Google\ Chrome" "Microsoft\ Word" )

for i in "${apps[@]}"
do
	killall $i
done
exit 0

when i generate verbose feedback, i'm seeing each app in question quit EXCEPT for those with spaces. on a mac, in the command line, i have to type the following to forcequit word and chrome:

Code:
killall Microsoft\ Word
killall Google\ Chrome

but i can't seem to find a way to paste the correct syntax into the array to get these applications to quit as the others do. in the above script example, the result just says:

"+ for i in '"${apps[@]}"'
+ killall 'Microsoft\' Word
No matching processes were found"

any thoughts on what i might be missing?
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Strange parameter passing problems (KSH)

Hi all, I'm having a rather peculiar problem involving parameter passing with declared functions in my shell script. Hope to get some advice here. A brief description of my code is as follows: However, I'm not getting the results I wanted. If I pass in $rdir, I'm going to end up... (4 Replies)
Discussion started by: rockysfr
4 Replies

2. UNIX for Dummies Questions & Answers

passing strings as arguments

Is it possible to pass a string as an argument from the command line? I know I can pass a word in but can I put a line of text in with spaces and fullstops or do I just put it in brackets or quotes so the compiler can differinate between the first argument and the second. (1 Reply)
Discussion started by: iago
1 Replies

3. Programming

array of strings

Hi I need a better idea to implementing following in my code. I need to store 80 long strings that will be used to display one by one in my GUI application. now i am storing those 80 long string in following two dimentational array. uchar vpn_alm_long_str={ } each index will be an... (1 Reply)
Discussion started by: davidcreston
1 Replies

4. Programming

Passing by value a char array

Hi I am passing or want to pass value of a char array, so that even thoug the called routine is changing the values the calling function should not see the values changed, meaning only copy should be passed Here is the program #include<iostream.h> #include<string.h> void f(char a); int... (5 Replies)
Discussion started by: rkraj
5 Replies

5. Shell Programming and Scripting

passing line into array

I am doing a shell script in ksh. I have an output from grep that goes something like this: wordIWasLookingFor anotherWordIWasLookingFor yetAnotherWordIWasLookingFor I want to toss each line into an array such that: myArray = wordIWasLookingFor myArray = anotherWordIWasLookingFor... (3 Replies)
Discussion started by: mrwatkin
3 Replies

6. Shell Programming and Scripting

Passing Array to awk

I'm trying to use the following command: awk -v array1=${array1} -f "filename.awk" input.txt Then within filename.awk I want to access array1. However, awk mistakes array1 (the third element of the array) for the input file. How I can pass awk this array? It also appears that awk scripts... (3 Replies)
Discussion started by: B-Ry
3 Replies

7. UNIX for Advanced & Expert Users

Passing full path as argument when it contains variable strings

Hi, In directory "inoutfiles", I have folders fold0001, fold0002 and so on. Every folder has corresponding file file0001.txt, file0002.txt and so on. I want to perform a certain action on multiple files in one go. The cpp file is in the same directory as "inoutfiles". This is my code : ... (0 Replies)
Discussion started by: KidD312
0 Replies

8. Programming

Passing full path as argument when it contains variable strings

Hi, In directory "inoutfiles", I have folders fold0001, fold0002 and so on. Every folder has corresponding file file0001.txt, file0002.txt and so on. I want to perform a certain action on multiple files in one go. The cpp file is in the same directory as "inoutfiles". This is my code : ... (1 Reply)
Discussion started by: KidD312
1 Replies

9. Shell Programming and Scripting

Bash Passing An Array

Good grief so this should be easy. Passing an array as an argument to a function. Here is the sample code: #/bin/bash function foo { local p1=${1} local p2=(${2}) local p3=${3} echo p1 is $p1 echo p2 is $p2 echo p3 is $p3 } d1=data1 d2=data2 a=(bat bar baz) (2 Replies)
Discussion started by: brsett
2 Replies

10. Shell Programming and Scripting

Problems passing shell arguments to perl

Semi-newbie, so flame throwers to 'singe-only', please. ;-) I have a large number of (say) .html files, where I'd like to do a recursive in-place search and replace a particular string. The following bit of perl works fine: perl -pi -e 's/oldstring/newstring/g' `find ./ -name *.html` ... (2 Replies)
Discussion started by: johnny_canucl
2 Replies

LEARN ABOUT REDHAT

killall

KILLALL(1)							   User Commands							KILLALL(1)

NAME

       killall - kill processes by name

SYNOPSIS

       killall [-e,--exact] [-g,--process-group] [-i,--interactive] [-q,--quiet] [-v,--verbose] [-w,--wait] [-V,--version] [-S,--sid] [-c,--con-
       text] [-s,--signal signal] [--] name ...
       killall -l
       killall -V,--version

DESCRIPTION

       killall sends a signal to all processes running any of the specified commands. If no signal name is specified, SIGTERM is sent.

       Signals can be specified either by name (e.g. -HUP) or by number (e.g. -1).

       If the command name contains a slash (/), processes executing that particular file will be selected for killing, independent of their name.

       killall returns a zero return code if at least one process has been killed for each ilisted command. killall returns zero otherwise.

       A killall process never kills itself (but may kill other killall processes).

OPTIONS

       -e, --exact
	      Require an exact match for very long names. If a command name is longer than 15 characters, the full name may be	unavailable  (i.e.
	      it  is  swapped  out). In this case, killall will kill everything that matches within the first 15 characters. With -e, such entries
	      are skipped.  killall prints a message for each skipped entry if -v is specified in addition to -e,

       -g, --process-group
	      Kill the process group to which the process belongs. The kill signal is only sent once per group, even if multiple processes belong-
	      ing to the same process group were found.

       -i, --interactive
	      Interactively ask for confirmation before killing.

       -l, --list
	      List all known signal names.

       -q, --quiet
	      Do not complain if no processes were killed.

       -v, --verbose
	      Report if the signal was successfully sent.

       -V, --version
	      Display version information.

       -w, --wait
	      Wait  for all killed processes to die. killall checks once per second if any of the killed processes still exist and only returns if
	      none are left.  Note that killall may wait forever if the signal was ignored, had no effect, or  if  the	process  stays	in  zombie
	      state.

       -S     (Flask  only) Specify SID: kill only processes with given SID. Mutually exclusive with -c argument.  Must precede other arguments on
	      command line.

       -c     (Flask only) Specify security context: kill only processes with given security context.  Mutually exclusive with -s.   Must  precede
	      other arguments on the command line.

FILES

       /proc	 location of the proc file system

KNOWN BUGS

       Killing by file only works for executables that are kept open during execution, i.e. impure executables can't be killed this way.

       Be warned that typing killall name may not have the desired effect on non-Linux systems, especially when done by a privileged user.

       killall -w doesn't detect if a process disappears and is replaced by a new process with the same PID between scans.

AUTHORS

       Werner  Almesberger  <Werner.Almesberger@epfl.ch>  wrote  the original version of psmisc.  Since version 20 Craig Small <csmall@small.drop-
       bear.id.au> can be blamed.

SEE ALSO

       kill(1), fuser(1), pgrep(1), pidof(1), ps(1), kill(2)

Linux								  March 25, 2001							KILLALL(1)
All times are GMT -4. The time now is 01:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy