Sponsored Content
Full Discussion: if not working correctly
Top Forums Shell Programming and Scripting if not working correctly Post 302116059 by 2dumb on Tuesday 1st of May 2007 11:53:21 AM
Old 05-01-2007
if not working correctly

Anyone have an idea why this if statement does not work correctly?

"test2.sh" 18 lines, 386 characters
#!/usr/bin/sh

WARNING=80
CRITICAL=95

check_it()
{
if [[ ${1} = ${WARNING} ]] || [[ ${1} -gt ${WARNING} && ${1} -lt ${CRITICAL} ]];then
echo "YES [[ ${1} = ${WARNING} ]] || [[ ${1} -gt ${WARNING} && ${1} -lt ${CRITICAL} ]]"
else
echo "NO [[ ${1} = ${WARNING} ]] || [[ ${1} -gt ${WARNING} && ${1} -lt ${CRITICAL} ]]"
fi
}

check_it 80.1
check_it 81.1

me> test2.sh
NO [[ 80.1 = 80 ]] || [[ 80.1 -gt 80 && 80.1 -lt 95 ]]
YES [[ 81.1 = 80 ]] || [[ 81.1 -gt 80 && 81.1 -lt 95 ]]
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Script not working correctly

I have a simple script that I want to run every 30 minutes but only when I execute it. I don't want it to be a crontab job. so i have for example date ls -l who sleep 1800 The first time it executes correctly but after the first time it nevers execute back again. It should execute after... (2 Replies)
Discussion started by: elchalateco
2 Replies

2. Shell Programming and Scripting

Variable not working correctly.

Hi, I have a script where I am trying to set a local variable using the following, MYVAR="$NAME"_"$NAME2".txt where say, NAME = one NAME2 = two so I want the output one_two.txt but what I am getting is, two.txt basically the $NAME2 is overwriting, what am I doing wrong? ... (3 Replies)
Discussion started by: walsh_j
3 Replies

3. Programming

Shell Implementation not working correctly

//save in/out int tmpin = dup(0); int tmpout = dup(1); //set initial input int fdin; if(_inputFile) { fdin = open(_inputFile, O_RDONLY | O_CREAT, S_IREAD | S_IWRITE); } else { //use default input fdin = dup(tmpin); } int ret; int fdout; for(int i = 0; i... (14 Replies)
Discussion started by: AirBronto
14 Replies

4. UNIX for Dummies Questions & Answers

grep -A switch not working correctly with -m

egrep -A 7 -m 2 -h 'Date:|Time:' *.html this is showing only 2 line after the context of the 2nd found match. Is this a bug in grep? egrep -A 7 -m 2 -h 'Time:' *.html - this works correctly (2 Replies)
Discussion started by: zer0
2 Replies

5. Shell Programming and Scripting

Find cmd not working correctly in script

I am trying to copy 2 types of files so I can archive them. I tested with a set of commands: touch -t $(date -d "-60 day" +%Y%m%d) WORKDIR/REF find TARGETDIR/ -type f -maxdepth 1 -iname \*.out\* -or -iname \*.log\* ! -newer WORKDIR/REF -exec ls -l {} \; This correctly lists any files in the... (2 Replies)
Discussion started by: prismtx
2 Replies

6. Shell Programming and Scripting

rsync is not correctly working

We are using Red Hat linux system. I am transferring my rman backup files to another server. Here is the command i am using to transfer the files. /usr/bin/rsync -avpP --delete /xyz/xyz/ 99.99.999.99::db110bkp Here is the rsync version. >rsync --version rsync version 3.0.6 ... (1 Reply)
Discussion started by: govindts
1 Replies

7. UNIX for Dummies Questions & Answers

Grep Regexp not working correctly

Consider the following code: grep -o -e '^STEAM_::\d+$' workfile3.tmp A sample format of a valid string for the regexp would be: STEAM_0:1:12345678 Here is an example line from the workfile3.tmp file: 465:L 01/02/2012 - 00:05:33: "Spartan1-1-7<8><STEAM_0:1:47539638><>" connected No... (2 Replies)
Discussion started by: spinner0205
2 Replies

8. Shell Programming and Scripting

awk not working correctly

Hi I am attempting to right a script which will read a table and extract specfic information. LASTFAILEDJOB=/usr/openv/netbackup/scripts/GB-LDN/Junaid/temp_files/lastfailedjob cat /usr/openv/netbackup/scripts/GB-LDN/Junaid/temp_files/lastfailedjob 237308646 If i run the following... (5 Replies)
Discussion started by: Junes
5 Replies

9. UNIX for Dummies Questions & Answers

vnc No Longer Working Correctly

Hello All, Yesterday, all day, I was using x11vnc and vncviewer to connect to a server. But today for some reason it is not working. I don't remember changing any settings or anything like that, but because it stopped working correctly I guess something has...? I'm issuing the exact same... (0 Replies)
Discussion started by: mrm5102
0 Replies

10. UNIX for Beginners Questions & Answers

Are the brains of the UNIXoid working correctly?

Today I saw the topic. sum-even-numbers-1-100 At that time, it was already closed but not the point. Other thoughts came to mind. All newcomers to Haskell are afraid that when they study it, their brains will turn inside out. I did not notice anything like that. And all because the brains of all... (4 Replies)
Discussion started by: nezabudka
4 Replies
clonefset(8)						      System Manager's Manual						      clonefset(8)

NAME
clonefset - Creates a read-only copy of an AdvFS fileset SYNOPSIS
/usr/sbin/clonefset domain fileset clonename OPERANDS
Specifies the name of an existing AdvFS file domain. Specifies the name of the original fileset that the clonefset utility will clone. Specifies the name of the read-only fileset created by the clonefset utility. DESCRIPTION
The clonefset utility enables you to perform online backups of active files by making a read-only copy (clone) of an active fileset. Once you create and mount a clone fileset, you can back up the clone using the vdump command or other supported backup utility (the dump command is not supported by AdvFS). Note that the clonefset utility only clones AdvFS filesets; it does not clone UFS file systems. A clone fileset is a read-only snapshot of fileset data structures (metadata). When you clone a fileset, the utility copies only the structure of the original fileset, not its data. When you modify files in the original fileset, the file system copies the original pages to the clone fileset. In this way, the clone fileset contents remain the same as when you first created it. You can create new versions of a clone fileset, but you can maintain only one clone per fileset at a time. You cannot rename a clone file- set, but there is a workaround. You can remove an existing clone fileset (and all its files) by using the rmfset command, then create a new one with the new name. RESTRICTIONS
Each fileset within a domain must have a unique name of up to 31 characters. All whitespace characters (tab, new line, space, and so forth) and the / # : * ? characters are invalid for fileset names. Do not create a clone fileset if the available disk space for the file domain is less than 5 percent of the total. When a file domain runs out of disk space, the file system loses its ability to maintain the consistency of files within clone filesets. When the file system can no longer maintain consistency, it displays warning messages similar to the following on the user's terminal and to the console: WARNING: advfs cannot copy-on-write data to a clone file. WARNING: encountered the following error: ENO_MORE_BLKS (-1040) WARNING: do not continue using the clone fileset. WARNING: original file set: name=mnt, id=2c06a73f.00027192.00000001.8001 WARNING: clone file set: name=clone, id=2c06a73f.00027192.00000002.8002 WARNING: file id = 0000000a.8002 This message also appears in the /var/adm/syslog.dated/latest_boot_date/kern.log file. EXAMPLES
The following example creates a read-only copy of the credit_fs fileset that resides in the accounts_dmn file domain. The clone fileset name in this example is credit_clone1. This example also performs an online backup and removes the clone fileset after the backup is com- plete: # mkdir /mnt/credit_clone1 # clonefset accounts_dmn credit_fs credit_clone1 # mount -t advfs account_dmn#credit_clone1 /mnt/credit_clone1 # vdump /mnt/credit_clone1 # umount /mnt/credit_clone1 # rmfset account_dmn credit_clone1 SEE ALSO
Commands: tar(1), showfdmn(8), vdump(8), vrestore(8) Functions: advfs_clonefset(3) File Formats: advfs(4) clonefset(8)
All times are GMT -4. The time now is 04:39 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy