10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Trying to do so
echo "111:222:333" |awk -F: '{system("export TESTO=" $2)}'But it doesn't work (2 Replies)
Discussion started by: urello
2 Replies
2. Shell Programming and Scripting
I have below data:
DAY1=10202013
I am trying below but not getting the desired output:
COUNT=1
DATE=DAY$COUNT
echo "Date is $DATE"
However output I am getting is:
Date is DAY1
I wanted the output as:
Date is 10202013
I tried following as well:
DAY1=10202013
COUNT=1... (3 Replies)
Discussion started by: rockyr1985
3 Replies
3. Shell Programming and Scripting
cat file
time="north_south_east_west_08:00" location="A" start="left" status="ok" end="north"
time="north_south_east_west_12:00" location="C" start="right" status="ok" end="south"
time="north_south_east_west_23:00" location="G" start="left" status="ok" end="east"... (7 Replies)
Discussion started by: ctphua
7 Replies
4. Shell Programming and Scripting
So I'm writing a script to generate pairwise scores for how similar two strings are, and while I've been able to get it to work on a single script, I've been unable to iterate it.
So suppose I have a file thus
1234567890
1234567890
1234567899
first I need to assign two lines, by their... (3 Replies)
Discussion started by: viored
3 Replies
5. Shell Programming and Scripting
HI ,I am a new in Bash and ,I dont know how to pass a second parameter to this fuction,if the name of the passed argument is num works fine,but if I try to pass secondNum,dont recognized it
thanks
function check()
{
if(($(echo ${#num}) == 0 ))
then
echo No arguments passed.Try... (6 Replies)
Discussion started by: lio123
6 Replies
6. UNIX for Dummies Questions & Answers
Hello all. I've been trying to install NWCHEM in parallel on a new cluster, and have been able to get it to work on single processors by ignoring any MPI environment variables.
This is, of course, pretty worthless. So I'm starting over and trying to get thing set up right for the MPI. The key... (6 Replies)
Discussion started by: EinsteinMcfly
6 Replies
7. Shell Programming and Scripting
Hi All,
I need to pass 2 variables name 'vamskt' and 'vamsi'.
Here is my question:
delete from gpi.usergroup where usg_user_id in ('vamskt');
delete from gpi.userroles where uro_user_id in ('vamskt');
delete from gpi.user where usr_id in ('vamskt');
insert into gpi.user... (3 Replies)
Discussion started by: tvamsikiran
3 Replies
8. Shell Programming and Scripting
HI all,
Very new to shell programming and just wanted some help on how to solve the following problem.
I have a small shell script which searches a given file and extracts some string parameters. I want to now be able to call this script from another shell script and somehow pass the parameters... (11 Replies)
Discussion started by: pxy2d1
11 Replies
9. Shell Programming and Scripting
Hi,
Is there any way to pass variable to a sed script.For awk we have -v option.like that do we have any way to pass variable to a sed script from a awk script or from normal script?
Thanx,
sounder (1 Reply)
Discussion started by: sounder123
1 Replies
10. Shell Programming and Scripting
Does anybody have an explanation for the following:
The following scripts runs fine on IRIX64 6.5 but has bugs on Solaris 8.
#! /bin/sh
echo run only on an SGI machine
echo type in linenumber
read j
echo value
read value
awk -f rmspass2 level=$value $j'step1.mlf'
When the script is... (5 Replies)
Discussion started by: AreaMan
5 Replies
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)