I have a strange issue here. I grep for 2 strings from a txt files and compare the string value. Though the string values are the same, they are compared as different values. Please help
Case-1
--------
Here I grep for 2 different field values and compare them. Though these 2 values are the same in the file, they are compared to be different values and I see the o/p as "Not Equal"
Code:
-----
tmp1=`grep Expected samFile.txt | head -1 | cut -d "," -f2 | sed 's/ //g'`
tmp2=`grep Expected samFile.txt | head -1 | cut -d "," -f4 | sed 's/ //g'`
if [[ "$tmp1" = "$tmp2" ]]
then
echo "Equal!!! "
else
echo "Not Equal!!! "
fi
Case-1
--------
Here I manually store these values directly to the variables. In this case, the comparison results is as expected, "Equal"
Code:
-----
tmp3=SAMPLE123
tmp4=SAMPLE123
if [[ "$tmp3" = "$tmp4" ]]
then
echo "Equal!!! "
else
echo "Not Equal!!! "
fi
Why didn't the strings were not equal in Case-1??
Last edited by vbe; 03-16-2011 at 02:14 PM..
Reason: Please use code tags!
hi ,
i am trying to compre two strings
if ] or if ]
when the length of var1 is small (around 300-400 char ) it works fine
but when it is large (around 900-1000 chars) it fails
is there any limitations for this type of comparison ??? (3 Replies)
hi ,
i am trying to compre two strings
if ] or if ]
when the length of var1 is small (around 300-400 char ) it works fine
but when it is large (around 900-1000 chars) it fails
is there any limitations for this type of comparison ??? (1 Reply)
Hello,
was just wondering how to compare strings in unix? I mean as in C there is a function strcmp() in string.h, is there any function in unix for that? I tried using
if
and all such variations but didn't succeed. Any help would be appreciated. Thanks in advance :) (9 Replies)
Hi Guys
i need to write a script to check the file structure
I have added the the file headers in the configuration file and execute the file at the start of the script.
Now the function
checkFileStructure()
{
echo "Inside the function"
filetocheck=$1
fileheader=$2
if ]
then... (1 Reply)
Hi,
I have the below logic. Here 'X' is a variable having some string.
if
then
echo "i dont need to go to ofc"
else
echo "i need to go to ofc"
Please help me to write it in unix.
Thanks. (2 Replies)
#!/bin/sh
PRINTF=/usr/bin/printf
MACHINE_NAME=`uname -n`
TIME=`date +"%H"`
$PRINTF "Welcome to $MACHINE_NAME. What is your name?\n"
read NAME
if ; then
$PRINTF "Good morning $NAME, how are you?\n"
elif ; then
$PRINTF "Good afternoon $NAME, how are you?\n"
else
$PRINTF "Good... (2 Replies)
continuing from my previous post, whose link is given below as a reference
https://www.unix.com/shell-programming-scripting/171076-shell-scripting.html#post302573569
consider there is create table commands in a file for eg:
CREATE TABLE `Blahblahblah` (
`id` int(11) NOT NULL... (2 Replies)
attempting the hangman program. This was an optional assignment from the professor. I have completed the logical coding, debugging now.
##I have an array $wordString that initializes to a string of dashes
##reflecting the number of letters in $theWord
##every time the user enters a (valid)... (5 Replies)
guys , i am using inotify for monitoring one directory to check core file generation , my snippet of code is follows
#!/bin/bash
DIR=$1
inotifywait -q -e create -m $DIR | while read path events name;
do
if ]; then
echo "Now I am going to do something with $name in directory $path."... (5 Replies)
I have the logic below to look up for matches within the columns between the two files with awk.
In the if statement is where the string comparison is attempted with ==
The issue seems to be with the operands, as
1. when " '${SECTOR}' " -- double quote followed by single quote -- awk matches... (1 Reply)
Discussion started by: deadyetagain
1 Replies
LEARN ABOUT DEBIAN
psiclean
psiclean(1)psiclean(1)NAME
psiclean - delete files in the PSI temporary directories
DESCRIPTION
The psiclean command finds a job name by scanning the input file for a keyword assignment of the form
DEFAULT:FILES:DEFAULT:NAME = string
It then goes through all of the machine's temporary directories and deletes all files of the form string.*. In previous versions of psi-
clean , temporary directories were assumed to be of the form
/tmp[0-9]/$user
In this version of psiclean , we get the names of the temporary directories from the user input file by looking for volume paths of the
form
DEFAULT:FILES:DEFAULT:VOLUMEi = string
It is essential that users see to the removal of their scratch files as soon as their job completes, because temporary directories are usu-
ally a shared resource and there is not necessarily an automatic way for files to be deleted from these areas. Thus, the last command run
after a job has finished should be the psiclean command.
The user must take care to follow certain conventions when choosing filenames. Any files which are to be kept after a job completes should
not be kept in the default temporary directories. The FILES input must be used to specify other locations for the specific files which are
to be kept. psiclean will ignore files which are specifically listed by number (e.g., PSIF_CHKPT ) in the FILES section. Files which are
not needed after the run should use the default path given in the input file. Otherwise, these files will remain on the system and will
impede other jobs.
EXAMPLE
Suppose the PSI temporary directories contained the following subdirectories and files:
/tmp1/cpuhog:
-rw-r--r-- 1 cpuhog 14492 Jun 11 16:48 dicubane.30
-rw-r--r-- 1 cpuhog 187320 Jun 8 17:20 diketene.34
-rw-r--r-- 1 cpuhog 16384 Jun 7 19:17 o4big.30
-rw-r--r-- 1 cpuhog 16384 Jun 7 19:17 o4.30
-rw-r--r-- 1 cpuhog 974848 Jun 7 18:41 o4.34
/tmp2/cpuhog:
-rw-r--r-- 1 cpuhog 14492 Jun 11 16:48 dicubane.30
-rw-r--r-- 1 cpuhog 187320 Jun 8 17:20 diketene.34
-rw-r--r-- 1 cpuhog 10904 Jun 7 18:50 o4big.30
-rw-r--r-- 1 cpuhog 10904 Jun 7 18:50 o4.30
-rw-r--r-- 1 cpuhog 973752 Jun 7 18:41 o4.34
/tmp3/cpuhog:
-rw-r--r-- 1 cpuhog 14492 Jun 11 16:48 dicubane.30
-rw-r--r-- 1 cpuhog 187320 Jun 8 17:20 diketene.34
-rw-r--r-- 1 cpuhog 8192 Jun 7 19:17 o4big.30
-rw-r--r-- 1 cpuhog 8192 Jun 7 19:17 o4.30
-rw-r--r-- 1 cpuhog 966656 Jun 7 18:41 o4.34
Let's also say that the user cpuhog is in a directory which contains an input file which has the following line in it:
DEFAULT:FILES:DEFAULT:NAME = "o4"
If the user cpuhog now executes the psiclean command, then the o4 files in the temporary directories would be deleted, leaving the follow-
ing files:
/tmp1/cpuhog:
-rw-r--r-- 1 cpuhog 14492 Jun 11 16:48 dicubane.30
-rw-r--r-- 1 cpuhog 187320 Jun 8 17:20 diketene.34
-rw-r--r-- 1 cpuhog 16384 Jun 7 19:17 o4big.30
/tmp2/cpuhog:
-rw-r--r-- 1 cpuhog 14492 Jun 11 16:48 dicubane.30
-rw-r--r-- 1 cpuhog 187320 Jun 8 17:20 diketene.34
-rw-r--r-- 1 cpuhog 10904 Jun 7 18:50 o4big.30
/tmp3/cpuhog:
-rw-r--r-- 1 cpuhog 14492 Jun 11 16:48 dicubane.30
-rw-r--r-- 1 cpuhog 187320 Jun 8 17:20 diketene.34
-rw-r--r-- 1 cpuhog 8192 Jun 7 19:17 o4big.30
AUTHOR
C. David Sherrill <sherrill@alum.mit.edu>
Psi Version 3.0 29 July, 1999 psiclean(1)