9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I am having check.sh script and check.service which I include to /etc/systemd/system/
chmod 744 /usr/local/bin/check.sh
chmod 664 /etc/systemd/system/check.service
systemctl daemon-reload
systemctl enable check.servicecheck.sh:
websockify 5555 localhost:7000 &
date >... (9 Replies)
Discussion started by: tomislav91
9 Replies
2. Shell Programming and Scripting
I can't quite find a clear answer on how to properly write a start up script. Does anybody have any ideas?? (3 Replies)
Discussion started by: Huitzilopochtli
3 Replies
3. Shell Programming and Scripting
The attached file is a copy of my rc.local. The rc.local script appears to execute as the tightvncserver gets started. However the nodemon process does not start. The element nodemon is a symlink to nodemon and the path is correct.
I have a little start script located in the... (3 Replies)
Discussion started by: barrygordon
3 Replies
4. Shell Programming and Scripting
I copied the script from an AskUbuntu post -
#!/bin/bash
### BEGIN INIT INFO
# Provides: tomcat7
# Required-Start: $network
# Required-Stop: $network
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start/Stop Tomcat server
### END INIT INFO
... (14 Replies)
Discussion started by: Hijanoqu
14 Replies
5. Red Hat
Hi, I am using scientific linux with is a red hat cloning.
I have written a script and I want it to be run during startup before the user log in.
How do I do that?
I know that there is some connection to the run level and the directory /etc/rc.d.
But I don't know how exactly to do it ?... (4 Replies)
Discussion started by: programAngel
4 Replies
6. AIX
Hi
I need the below script to be started whenever I reboot my aix server ?
#cat cdbegin
/cdirect/cdunix/ndm/bin/cdpmgr -i /cdirect/cdunix/ndm/cfg/cbspsdb01/initparm.cfg
Please suggest how to add this to the startup ? (2 Replies)
Discussion started by: samsungsamsung
2 Replies
7. Solaris
Hi All,
O/S: Solaris 5.10
Software installed :-
Oracle 10G
Weblogic 10.30
the problem i face that
when the server restart for any reason
SQL> exit
bash-3.00# sqlplus sys/manchester as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Sun May 2 11:04:50 2010
Copyright (c)... (3 Replies)
Discussion started by: xxmasrawy
3 Replies
8. AIX
Guy's
What the exact steps to mention for example this script /usr/start/start.sh
to be as start up script , I want it to be automatically started when I reboot the server . (8 Replies)
Discussion started by: ITHelper
8 Replies
9. Shell Programming and Scripting
New in Unix, I am adding a line "route add 57.14.y.y 57.14.x.x" every day after rebooting the system. Where can I add the line so during boot up (the system is re-started every day by design (???) the line is executed? (I tried the /etc/rc2.d/S90 but for some reason the line needs to be added... (2 Replies)
Discussion started by: texaspanama
2 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)