04-12-2002
Need help with if [ ] in my script?
In the following sccript I want to be able to only send different notifications based in whether the filesyste is over 80% or 90%. I need help with if [ ]. How would I make it so that if a filesystem was over 80% but less than 90% only do one thing. The way I currently have it setup I end up getting double notifications when a filesystem is over 90%.
#!/bin/bash
host=`uname -n`
NOTIFYEMAIL="joe.blow@me.com"
NOTIFYPAGE="joe.blow@me.com"
# Notification message
root_msg="FileSystem `df -h / | tail -1 | awk '{print $1 " is " $5 " Utilized Mounted on " $6 " with a Size of " $2 " has Used " $3 " Leaving only " $4 " of Available Space. "}'`"
# Set Severity level
sev1_Alarm="mailx -s $host $NOTIFYPAGE $NOTIFYEMAIL"
sev2_Warn="mailx -s $host $NOTIFYEMAIL"
# Extract filesystem % full integer
rootuse=`df -h / | awk '{print $5}' | cut -c1-2 | grep '[0-9]'`
# / filesystem
if [ "$rootuse" -gt "80" ]
then
echo $root_msg | $sev2_Warn
if [ "$rootuse" -gt "90" ]
then
echo $root_msg | $sev1_Alarm
fi
fi
5 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi guys
I have a shell script that executes sql statemets and sends the output to a file.the script takes in parameters executes sql and sends the result to an output file.
#!/bin/sh
echo " $2 $3 $4 $5 $6 $7
isql -w400 -U$2 -S$5 -P$3 << xxx
use $4
go
print"**Changes to the table... (0 Replies)
Discussion started by: magikminox
0 Replies
2. Shell Programming and Scripting
I am using blow script :--
#!/bin/bash
FIND=$(ps -elf | grep "snmp_trap.sh" | grep -v grep) #check snmp_trap.sh is running or not
if
then
# echo "process found"
exit 0;
else
echo "process not found"
exec /home/Ketan_r /snmp_trap.sh 2>&1 & disown -h ... (1 Reply)
Discussion started by: ketanraut
1 Replies
3. UNIX for Dummies Questions & Answers
I am trying to call a script(callingscript.sh) from a master script(masterscript.sh) to get string type value from calling script to master script. I have used scripts mentioned below.
#masterscript.sh
./callingscript.sh
echo $fileExist
#callingscript.sh
echo "The script is called"... (2 Replies)
Discussion started by: Raj Roy
2 Replies
4. Shell Programming and Scripting
Hello all,
I am facing a weird issue while executing a code below -
#!/bin/bash
cd /wload/baot/home/baotasa0/sandboxes_finance/ext_ukba_bde/pset
sh UKBA_publish.sh UKBA 28082015 3
if
then
echo "Param file conversion for all the areas are completed, please check in your home directory"... (2 Replies)
Discussion started by: ektubbe
2 Replies
5. Shell Programming and Scripting
I'm new to utilities like socat and netcat and I'm not clear if they will do what I need.
I have a "compileDeployStartWebServer.sh" script and a "StartBrowser.sh" script that are started by emacs/elisp at the same time in two different processes.
I'm using Cygwin bash on Windows 10.
My... (3 Replies)
Discussion started by: siegfried
3 Replies
LEARN ABOUT X11R4
xfs_logprint
xfs_logprint(8) System Manager's Manual xfs_logprint(8)
NAME
xfs_logprint - print the log of an XFS filesystem
SYNOPSIS
xfs_logprint [ options ] device
DESCRIPTION
xfs_logprint prints the log of an XFS filesystem (see xfs(5)). The device argument is the pathname of the partition or logical volume con-
taining the filesystem. The device can be a regular file if the -f option is used. The contents of the filesystem remain undisturbed.
There are two major modes of operation in xfs_logprint.
One mode is better for filesystem operation debugging. It is called the transactional view and is enabled through the -t option. The
transactional view prints only the portion of the log that pertains to recovery. In other words, it prints out complete transactions
between the tail and the head. This view tries to display each transaction without regard to how they are split across log records.
The second mode starts printing out information from the beginning of the log. Some error blocks might print out in the beginning because
the last log record usually overlaps the oldest log record. A message is printed when the physical end of the log is reached and when the
logical end of the log is reached. A log record view is displayed one record at a time. Transactions that span log records may not be
decoded fully.
OPTIONS
-b Extract and print buffer information. Only used in transactional view.
-c Attempt to continue when an error is detected.
-C filename
Copy the log from the filesystem to the file filename. The log itself is not printed.
-d Dump the log from front to end, printing where each log record is located on disk.
-D Do not decode anything; just print data.
-e Exit when an error is found in the log. Normally, xfs_logprint tries to continue and unwind from bad logs. However, sometimes it
just dies in bad ways. Using this option prevents core dumps.
-f Specifies that the filesystem image to be processed is stored in a regular file at device (see the mkfs.xfs(8) -d file option).
This might happen if an image copy of a filesystem has been made into an ordinary file with xfs_copy(8).
-l logdev
External log device. Only for those filesystems which use an external log.
-i Extract and print inode information. Only used in transactional view.
-q Extract and print quota information. Only used in transactional view.
-n Do not try and interpret log data; just interpret log header information.
-o Also print buffer data in hex. Normally, buffer data is just decoded, so better information can be printed.
-s start-block
Override any notion of where to start printing.
-t Print out the transactional view.
SEE ALSO
mkfs.xfs(8), mount(8).
xfs_logprint(8)