It is recommended always to use the variable with quotes especially during comparison to avoid such errors . Am I right ?
Pretty much, though analytically, you can see that the variable will contain something. However, someone can change the code that breaks that condition.... so better to always quote.
You can also do this trick, often seen in older scripts:
Instead of quoting the variable, you pre- or postfix something to it AND the thing you compare it to.
Hi,
I have this following script below. Its searching a log file for 2 string and if found then write the strings to success.txt and If not found write strings to failed.txt . if one found and not other...then write found to success.txt and not found to failed.txt.
I want to optimize this... (3 Replies)
I've a script to do some snapshots but the time it does so is very different...
once i got a snapshot under 1 sec, on the other hand it took 3 sec, but nothing else changed, i didnt even move the cursor or something.
I put the script on a ramdisk and its faster, but still swing from under 1... (1 Reply)
Hi All,
There is a script (test.sh) which is taking more CPU usage. I am attaching the script in this thread.
Could anybody please help me out to optimize the script in a better way.
Thanks,
Gobinath (6 Replies)
Dear Forum experts
I have the below script which I made to run under bash shell, it runs perfectly for low records number, let us say like 100000. when I put all records (3,000,000), it's takes hours
can you please suggest anything to optimize or to run in different way :-|
{OFS="|";... (6 Replies)
Here is my code. What it does is it reads an input file (input.txt which contains roughly 2,000 search phrases) and searches a directory for files that contains the search phrase. The directory contains roughly 1900 files and 84 subdirectories. The output is a file (output.txt) that shows only the... (23 Replies)
Hi,
I need a shell script to determine if a no. is either even, greater than 4, less than 8
SHELL : ksh
OS : RHEL 6
this is the if block of the script
mod=`expr $num % 2`
if || ||
then
echo "No. is either even or greater than 4 or less than 8"
fi
this code works... (2 Replies)
Hello,
I'm wondering if there is a quicker way of doing this.
Here is my mv script.
d=/conversion/program/out
cd $d
ls $d > /home/tempuser/$$tmp
while read line ; do
a=`echo $line|cut -c1-5|sed "s/_//g"`
b=`echo $line|cut -c16-21`
if ;then mkdir... (13 Replies)
Hi All,
I have written a new script to check for DB space and size of dump log file before it can be imported into a Oracle DB.
I'm relatively new to shell scripting.
Please help me optimize this script further. (0 Replies)
Hi Friends,
I'm trying to create a script that allows me to recursively resize, crop (holding the center of the image) and optimize images jpg, jpeg, png for a specific folder and subfolder with the ability to exclude certain folder and its subdirectory.
Again, I should to do with this script:... (3 Replies)
Discussion started by: danjde
3 Replies
LEARN ABOUT CENTOS
pmdasimple
PMDASIMPLE(1) General Commands Manual PMDASIMPLE(1)NAME
pmdasimple - simple performance metrics domain agent (PMDA)
SYNOPSIS
$PCP_PMDAS_DIR/simple/pmdasimple [-d domain] [-i port] [-l logfile] [-p] [-u socket] [-U username]
DESCRIPTION
pmdasimple is a simple Performance Metrics Domain Agent (PMDA) which exports a small number of synthetic performance metrics.
The simple PMDA is shipped as source code and is designed to be an aid for PMDA developers. In terms of code size and features, it is more
complex than the trivial PMDA, about the same as the txmon PMDA and less complex than the sample PMDA. The source for the simple PMDA is a
good template from which production, customized PMDAs can be developed.
A brief description of the pmdasimple 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.
-i Expect PMCD to connect to pmdasimple on the specified TCP/IP port. port may be a port number or port name.
-l Location of the log file. By default, a log file named simple.log is written in the current directory of pmcd(1) when pmdasimple 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.
-p Expect PMCD to create a pipe and the connection to pmdasimple is via standard input and standard output. This is the default connec-
tion mode.
-u Expect PMCD to connect to pmdasimple on the Unix domain socket named socket.
-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.
At most one of the options -i, -p and -u may be specified.
INSTALLATION
If you want access the names, help text and values for the simple performance metrics, do the following as root:
# cd $PCP_PMDAS_DIR/simple
# ./Install
If you want to undo the installation, do the following as root:
# cd $PCP_PMDAS_DIR/simple
# ./Remove
pmdasimple 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.
FILES
$PCP_PMCDCONF_PATH
command line options used to launch pmdasimple
$PCP_PMDAS_DIR/simple/help
default help text file for the simple metrics
$PCP_PMDAS_DIR/simple/Install
installation script for the pmdasimple agent
$PCP_PMDAS_DIR/simple/Remove
undo installation script for the pmdasimple agent
$PCP_PMDAS_DIR/simple/simple.conf
configuration file for the dynamic instance domain that underlies the simple.now performance metric. For a description, refer to
the help text file, or run the command
$ pminfo -T simple.now
$PCP_PMDAS_DIR/simple/*.pmda_simple.so
The DSO version of the PMDA. The same source is used to create both the DSO and the daemon versions of the simple PMDA, and one
or the other may be installed as part of the dialog in the Install script.
$PCP_LOG_DIR/pmcd/simple.log
default log file for error messages and other information from pmdasimple
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 PCPIntro(1), pmcd(1), pmdasample(1), pmdatrivial(1), pmdatxmon(1), PMDA(3), pcp.conf(5) and pcp.env(5).
Performance Co-Pilot PCP PMDASIMPLE(1)