basically what this script is supposed to do is showing a list of hosts that is given a number, that you will be able to choose from a list.
A check is made to verify that the chosen number is within the array and this is where things go bad and I don't know why, bizarre.
I've spent quite some time trying to figure out why this function doesn't give the correct output (see below the script).
Code:
HOSTLIST="test1 test2 test3"
List_Hosts ()
{
num=1
hosts=
HI_HOSTS=
hostlist=(NULL $( echo $HOSTLIST ))
hostnumbers=${#hostlist[@]}
for (( i=1; i<${hostnumbers}; i++ )); do
hosts=$( echo "$hosts($num)-${hostlist[$i]} " )
let num=num+1
done
echo -e "\n$hosts\n"
echo -n "Enter number(s) (comma-separated - 1,2,3): "
read input
if [ -n "$( echo "$input" | tr , " " | tr -d '[0-9]' | awk '{print $1}' )" ]; then
echo -e "\nNone numerical value \"$input\" entered, please try again."
List_Hosts
else
for hostnum in $( echo "$input" | tr , " " ) ; do
if [ "$hostnum" -eq 0 -o "$hostnum" -gt $[$hostnumbers-1] ]; then
echo "Number \"$hostnum\" doesn't match existing values, please try again."
List_Hosts
fi
HI_HOSTS=$( echo "$HI_HOSTS${hostlist[$hostnum]} " )
done
fi
}
List_Hosts
echo $HI_HOSTS
Enter number(s) (comma-separated - 1,2,3): 4
Number "4" doesn't match existing values, please try again.
(1)-test1 (2)-test2 (3)-test3
Enter number(s) (comma-separated - 1,2,3): 5
Number "5" doesn't match existing values, please try again.
(1)-test1 (2)-test2 (3)-test3
Enter number(s) (comma-separated - 1,2,3): 1,2
test1 test2 test2 test2 for each unmatched number it will add the last entry again. Running it without typing an unmatched number it will give the correct output.
My script is erroring with: testtapemgr.sh: FTP_RETURNS: not found
I cannot see what I am doing wrong..when it calls that function from the Volume returns function and says taht FTP_RETURNS is not found and exits out of the script. What am I not seeing here?
#### Return Volume Function ... (4 Replies)
Passing a array to a function, a basic feature in modern language, seems to be only possible in KSH. Not in BASH. Depite all my efforts I couldn't come to a solution. See the following examples:
It works perfectly in KSH:
#!/usr/bin/ksh
function print_array {
# assign array by indirect... (3 Replies)
Hello!
I have a question about loops and arrays. I'm trying to go through this:
for aa in 01 02 03
OrigNum=$(grep ${Orig} Ba3In2F12.prepos | wc -l)
OrigNum=$((${OrigNum} - 1))
echo ${OrigNum}
etc
It gets stuck on the second line. The error reads:
./asdf: line 30:... (5 Replies)
Hi,
I'm trying to write a function that reassigns an array to
another local array but the method used in reassigning
the array reformats the contents of the array which is
what I am trying to prevent.
The method used to load a file into an array works as
expected and the entire array is... (4 Replies)
Can anybody tell me where is the bug in this below mentioned function call.
#The String Search File
myString="${LOCATION}/config/stringFile.txt"
# Functional Usage
function usage() {
if ; then
echo "************************************************************"
... (5 Replies)
In one session I have strange behavior of the bash-shell:
SDX-Q> echo ">$ss<" #this is just to present the $ss var:
> lll kkk <
SDX-Q> # more obviose:
SDX-Q> od -cb <<<"$ss"
0000000 l l l k k k \n
040 040 040 154 154 154 040... (3 Replies)
Hello there
i have a funny behiavor of the sort fonction, i try it out on different Solaris machine and i have the same issue.
So i would like to see if there is a rationel explanation
here is some data in a file:test.txt
,Test,RSD,RSD_Asset
,Test,RSD,RSD_Credit
,Test,RSD,RSD_Liab... (3 Replies)
Hello, first time here. I have a script that seems to ignore the if statement when run from the cron. I am using Ubuntu 12.10
#!/bin/bash
DOWN=/usr/sbin/dcon
UP="pon dsl-provider"
LOG=/var/log/dsl-reconnect.log
RECV=`ifconfig 2>&1|grep ppp0|cut -d , -f 5|cut -d " " -f 1`
if ]
then... (1 Reply)
Hey,
There was a small bug in the Quick Editor function in postbit, but I fixed it (basically a double quote was missing from an element id):
<div id="post_message_$post" class="neo-message-area">$post</div>
Was
<div id="post_message_$post class="neo-message-area">$post</div>
Should... (1 Reply)
Discussion started by: Neo
1 Replies
LEARN ABOUT CENTOS
pmdabash
PMDABASH(1) General Commands Manual PMDABASH(1)NAME
pmdabash - Bourne-Again SHell trace performance metrics domain agent
SYNOPSIS
$PCP_PMDAS_DIR/bash/pmdabash [-C] [-d domain] [-l logfile] [-I interval] [-t timeout] [-U username] configfile
DESCRIPTION
pmdabash is an experimental Performance Metrics Domain Agent (PMDA) which exports "xtrace" events from a traced bash(1) process. This
includes the command execution information that would usually be sent to standard error with the set -x option to the shell.
Event metrics are exported showing each command executed, the function name and line number in the script, and a timestamp. Additionally,
the process identifier for the shell and its parent process are exported.
This requires bash version 4 or later.
A brief description of the pmdabash command line options follows:
-d It is absolutely crucial that the performance metrics domain number specified here is unique and consistent. That is, domain should
be different for every PMDA on the one host, and the same domain number should be used for the same PMDA on all hosts.
-l Location of the log file. By default, a log file named bash.log is written in the current directory of pmcd(1) when pmdabash is
started, i.e. $PCP_LOG_DIR/pmcd. If the log file cannot be created or is not writable, output is written to the standard error
instead.
-s Amount of time (in seconds) between subsequent evaluations of the shell trace file descriptor(s). The default is 2 seconds.
-m Maximum amount of memory to be allowed for each event queue (one per traced process). The default is 2 megabytes.
-U User account under which to run the agent. The default is the unprivileged "pcp" account in current versions of PCP, but in older
versions the superuser account ("root") was used by default.
INSTALLATION
In order for a host to export the names, help text and values for the bash performance metrics, do the following as root:
# cd $PCP_PMDAS_DIR/bash
# ./Install
As soon as an instrumented shell script (see INSTRUMENTATION selection below) is run, with tracing enabled, new metric values will appear -
no further setup of the agent is required.
If you want to undo the installation, do the following as root:
# cd $PCP_PMDAS_DIR/bash
# ./Remove
pmdabash is launched by pmcd(1) and should never be executed directly. The Install and Remove scripts notify pmcd(1) when the agent is
installed or removed.
INSTRUMENTATION
In order to allow the flow of event data between a bash(1) script and pmdabash, the script should take the following actions:
#!/bin/sh
source $PCP_DIR/etc/pcp.sh
pcp_trace on $@ # enable tracing
echo "awoke, $count"
pcp_trace off # disable tracing
The tracing can be enabled and disabled any number of times by the script. On successful installation of the agent, several metrics will
be available:
$ pminfo bash
bash.xtrace.numclients
bash.xtrace.maxmem
bash.xtrace.queuemem
bash.xtrace.count
bash.xtrace.records
bash.xtrace.parameters.pid
bash.xtrace.parameters.parent
bash.xtrace.parameters.lineno
bash.xtrace.parameters.function
bash.xtrace.parameters.command
When an instrumented script is running, the generation of event records can be verified using the pmevent(1) command, as follows:
$ pmevent -t 1 -x '' bash.xtrace.records
host: localhost
samples: all
bash.xtrace.records["4538 ./test-trace.sh 1 2 3"]: 5 event records
10:00:05.000 --- event record [0] flags 0x19 (point,id,parent) ---
bash.xtrace.parameters.pid 4538
bash.xtrace.parameters.parent 4432
bash.xtrace.parameters.lineno 43
bash.xtrace.parameters.command "true"
10:00:05.000 --- event record [1] flags 0x19 (point,id,parent) ---
bash.xtrace.parameters.pid 4538
bash.xtrace.parameters.parent 4432
bash.xtrace.parameters.lineno 45
bash.xtrace.parameters.command "(( count++ ))"
10:00:05.000 --- event record [2] flags 0x19 (point,id,parent) ---
bash.xtrace.parameters.pid 4538
bash.xtrace.parameters.parent 4432
bash.xtrace.parameters.lineno 46
bash.xtrace.parameters.command "echo 'awoke, 3'"
10:00:05.000 --- event record [3] flags 0x19 (point,id,parent) ---
bash.xtrace.parameters.pid 4538
bash.xtrace.parameters.parent 4432
bash.xtrace.parameters.lineno 47
bash.xtrace.parameters.command "tired 2"
10:00:05.000 --- event record [4] flags 0x19 (point,id,parent) ---
bash.xtrace.parameters.pid 4538
bash.xtrace.parameters.parent 4432
bash.xtrace.parameters.lineno 38
bash.xtrace.parameters.function "tired"
bash.xtrace.parameters.command "sleep 2"
FILES
$PCP_PMCDCONF_PATH
command line options used to launch pmdabash
$PCP_PMDAS_DIR/bash/help
default help text file for the bash metrics
$PCP_PMDAS_DIR/bash/Install
installation script for the pmdabash agent
$PCP_PMDAS_DIR/bash/Remove
undo installation script for pmdabash
$PCP_LOG_DIR/pmcd/bash.log
default log file for error messages and other information from pmdabash
PCP ENVIRONMENT
Environment variables with the prefix PCP_ are used to parameterize the file and directory names used by PCP. On each installation, the
file /etc/pcp.conf contains the local values for these variables. The $PCP_CONF variable may be used to specify an alternative configura-
tion file, as described in pcp.conf(5).
SEE ALSO bash(1), pmevent(1) and pmcd(1).
Performance Co-Pilot PCP PMDABASH(1)