I have searched and found a few threads that have dealt with this, but the examples I've tried haven't seemed to help.
I am monitoring our database log for high checkpoints.
I can parse out the checkpoint value which can be anywhere from zero into a 3 digit number.
I set a variable to be the... (3 Replies)
Script
#!/bin/sh
hardware=PC
os=WindowsNET
for i in `cat newservers`
do
x=`sudo /opt/openv/netbackup/bin/admincmd/bpplclients |grep $i |head -40 |grep $i|awk '{print $3;exit}'`
if
then
echo "$i is already added"
else
echo "Need to add"
fi
done
O/p in debug mode
bash-2.05$... (3 Replies)
im trying to compare ipaddresses. i loop through an array to see if the ip is already is in the array and if it is it should set a flag and then i wont add it to the array. but its just adding all the ipaddresses to the array
if ]
then
... (3 Replies)
I'm writing a shellscript that monitors the price of a watch. If the prices changes, it should email me. The body of the email will show the old price and the new price. However when I compare the two awk variables(oldprice and newprice) it always says they're not the same. The shellscript goes out... (2 Replies)
Hi!
I've come up with a ksh-script that produces one or more lists of hosts.
At the and of the script, I would like to print only those hosts that exists in all the lists.
Ex.
HOSTS="host1 host2 host3 host11"
HOSTS="host1 host2 host4"
HOSTS="host2 host11"
HOSTS="host2 host5 host6 host7... (1 Reply)
Hi,
I am a noob at shell scripting.
basically I am trying to compare row counts from 8 tables in different databases. I have managed to get the row counts using awk from the spool files for both databases.
now I have 16 variables with me
for database 1 :
$A
$B
$C
$D
$E
$F
$G... (3 Replies)
hi
i am writing a hangman script and am having trouble checking the correct letters against the word
i need the script to compare the word against the letters guessed that are correct so once all the letters within the word have been guessed it will alow me to create a wining senario
eg
... (13 Replies)
Is there a way to compare variables in a 'awk'?
I've been trying for a while and can't figure it out. I'm guessing its not possible :/
VAR=Bob
awk '$3 == $VAR { print $1 }' file.txt
Regards
Jikuu (4 Replies)
I have a script like this. Just couldn't get the comparison part work. Any thought? thanks,
#!/usr/bin/ksh -x
STEP=`echo $(basename $0 .ksh) | tr "" ""`
log=/skip.log
while read LINE
do
if
then
echo `date`: STEP $STEP skipped by user >> $log
exit 0
fi
done < $1
echo... (0 Replies)
Perl::Critic::Policy::Variables::ProhibitEvilVariables(3User Contributed Perl DocumentatiPerl::Critic::Policy::Variables::ProhibitEvilVariables(3)NAME
Perl::Critic::Policy::Variables::ProhibitEvilVariables - Ban variables that aren't blessed by your shop.
AFFILIATION
This Policy is part of the core Perl::Critic distribution.
DESCRIPTION
Use this policy if you wish to prohibit the use of specific variables. These may be global variables warned against in "perlvar", or just
variables whose names you do not like.
CONFIGURATION
The set of prohibited variables is configurable via the "variables" and "variables_file" options.
The value of "variables" should be a string of space-delimited, fully qualified variable names and/or regular expressions. An example of
prohibiting two specific variables in a .perlcriticrc file:
[Variables::ProhibitEvilVariables]
variables = $[ $^S $SIG{__DIE__}
If you prohibit an array or hash (e.g. @INC), use of elements of the array or hash will be prohibited as well. If you specify a subscripted
variable (e.g. $SIG{__DIE__}), only the literal subscript specified will be detected. The above <.perlcritic> file, for example, will
cause "perlcritic (1)" to detect "$SIG{__DIE__} = &foo", but not
my $foo = '__DIE__';
$SIG{$foo} = &foo;
Regular expressions are identified by values beginning and ending with slashes. Any variable with a name that matches "m/pattern/sm" will
be forbidden. For example:
[Variables::ProhibitEvilVariables]
variables = /acme/
would cause all variables that match "m/acme/" to be forbidden. If you want a case-blind check, you can use (?i: ... ). For example
[Variables::ProhibitEvilVariables]
variables = /(?i:acme)/
forbids variables that match "m/acme/smi".
In addition, you can override the default message ("Prohibited variable "variable" used") with your own, in order to give suggestions for
alternative action. To do so, put your message in curly braces after the variable name or regular expression. Like this:
[Variables::ProhibitEvilVariables]
variables = $[ {Found use of $[. Program to base index 0 instead}
If your message contains curly braces, you can enclose it in parentheses, angle brackets, or square brackets instead.
Similarly, the "variables_file" option gives the name of a file containing specifications for prohibited variables. Only one variable
specification is allowed per line and comments start with an octothorp and run to end of line; no curly braces are necessary for delimiting
messages:
$[ # Prohibit the "$[" variable and use the default message.
# Prohibit the "$^S" variable and give a replacement message.
$^S Having to think about $^S in exception handlers is just wrong
# Use a regular expression.
/acme/ No coyotes allowed.
By default, there are no prohibited variables, although I can think of a few that should be. See "perldoc perlvar" for a few suggestions.
RESTRICTIONS
Variables of the form "${^foo}" are not recognized by PPI as of version 1.206. When PPI recognizes these, this policy will Just Work for
them too.
Only direct references to prohibited variables and literal subscripts will be recognized. For example, if you prohibit $[, the first line
in
my $foo = $[;
$$foo = 1;
will be flagged as a violation, but not the second, even though the second, in fact, assigns to $[. Similarly, if you prohibit
$SIG{__DIE__}, this policy will not recognize
my $foo = '__DIE__';
$SIG{$foo} = sub {warn 'I cannot die!'};
as an assignment to $SIG{__DIE__}.
NOTES
This policy leans heavily on Perl::Critic::Policy::Modules::ProhibitEvilModules by Jeffrey Ryan Thalhammer.
AUTHOR
Thomas R. Wyant, III wyant at cpan dot org
COPYRIGHT
Copyright (c) 2009-2011 Thomas R. Wyant, III
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. The full text of this license
can be found in the LICENSE file included with this module.
perl v5.16.3 2014-06-09 Perl::Critic::Policy::Variables::ProhibitEvilVariables(3)