I copied it into a file I call watch-running-process
Here is a driver script:
The parameters are the PID you are watching, the volume of the source in MB, and an optional delay for the loop (default 5 seconds). Because you supply the PID, you can run anything you want, just as long as it does io that is captured in /proc (so not Solaris, macOS, BSD, etc.). I have not looked in detail at the numbers in /proc, but the script seems to work. If you are interested / curious, see man proc, look at the entry for io, read_bytes, etc.
Here are display snapshots near the beginning, middle, and end of the process for cp as done prior to the call to the monitoring script:
There is not a real progress bar, but it includes an ETA, along with data rates. Given that the numbers are all available in the script, a scaled progress bar probably could be done.
Hello once again:
One thing that seems to be a nice feature is a progress gauge... so I can see how long an operation will take for a task to complete if it is requiring a lot of processing or the file is enormous. I have seen references to gauge operations, but I don't know anything about it or... (1 Reply)
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
This is a problem I am having with my 2 semester senior project. I have a LAMP server running Ubuntu 9.10 with... (8 Replies)
hey everyone, new here
i have arch setup and i am using smbnetfs to mount some windows shares in /mnt/smbnet
what i want to do is copy files from my home dir to a dir in /mnt/smbnet but i also need it to remove files if i have deleted them from my home dir
seems that cp would be the... (8 Replies)
Hi,
This is my program.
#!/bin/bash
today=`date +"%b-%d-%Y"`
SERVICE="pbxconnect.php"
if ; then
echo "pbx program is running"
else
nohup php pbxconnect.php > logpbx-$today.txt &
fi
On executing using "sh myprogram.sh" , i get the following error.
myprogram.sh: line 4: '
My... (7 Replies)
I'm a bit new to bash programming and I was assigned the job of writing a script that will check to see if a program server is running and to restart the program if it is not up. The script is supposed to check the program every hour (which I have looked up and I believe I know how to do) and send... (3 Replies)
I just can't figure it out , so please just give me a pice of advise how to:
The existing Linux program foo2bar takes as its only argument the name of a single foo file and converts it to an appropriately-named bar file. Provide a script that when executed will run foo2bar against all foo... (4 Replies)
I'm trying to write a script the simplifies the execution of a program:
After starting the program (sh ~/.mfix/model/make_mfix) I am prompted four times for options:
Do you need SMP version? (y/n)
Do you need DMP version? (y/n)
Do you need debug version? (y/n)
Force re-compilation of... (2 Replies)
suppose i have a bash script:
#!/bin/bash
echo "hello"
echo "how are you"
echo "today"
how can i put the entire script above into a basic c program?
i do not want to translate the bash code to a c code. i want C to run the bash code. is this possible?
i found this on the... (15 Replies)
I wish to be able to give to a client the opportunity to :
0) Turn one of my ubuntu computers into a webserver
1) See a webpage after visiting a url where an external user/client can set a couple of variables (e.g. Number1= ?, Number2=?)
2) By pressing "run" the program runs on my machine
3)... (1 Reply)
I am working on a script to get the final total size and so far have the following and wondering if this can be improved.
# Compare the desired size of each lvm to the standard size. If it is desired is larger than calculate the difference and keep that value as the amount to add to that LVM. ... (5 Replies)
Discussion started by: user3528
5 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)