I am VERY much a neophyte with shell scripting. I am working on the following,
"Create a script sends an email message to the user specified on the command line if any of the file
systems at more than 60% of capacity. The script should not process special file systems as /proc on
the ce.uml.edu. It should only process file systems which are either locally mounted or are mounted
via NFS."
This is my starting point:
Code:
#!/bin/bash
# script to send an email message to the user specified on the command line if
# any of the file systems at more than 60% of capacity.
df -H | grep -vE '^Filesystem' | 'none' | awk '{ print $1 " " $5 }' | while read fsout
do
echo "$fsout"
partition=$(echo "$fsout" | awk '{ print $2 }' )
usage=$(echo "$fsout" | awk '{ print $1 }' | cut -d'%' -f1)
if [ $usage -ge 90 ]
then
echo "CRITICAL WARNING!!: Filesystem \"$partition\" at "$usage"% of capacity" |
mail -s "CRITICAL WARNING!!: Filesystem \"$partition\" at "$usage"% of capacity" paul_peterson@student.uml.edu
elif [ $usage -ge 60 ] && [ $usage -lt 90 ]
then
echo "Warning!!: Filesystem \"$partition\" at "$usage"% of capacity" |
mail -s "Warning!!: Filesystem \"$partition\" at "$usage"% of capacity" paul_peterson@student.uml.edu
fi
done
I ma getting these errors:
Code:
./fsc.sh: line 4: $'\r': command not found
./fsc.sh: line 16: syntax error near unexpected token `elif'
'/fsc.sh: line 16: ` elif [ $usage -ge 60 ] && [ $usage -lt 90 ]
Any help is greatly appreciated.
Moderator's Comments:
Please use CODE tags as required by forum rules!
Last edited by RudiC; 02-25-2018 at 01:17 PM..
Reason: Added CODE tags.
Hi,
If we want to debug a shell script, then set -vx has to be included in the begining of the script. Just i want to know what purpose -vx is used.
Thanks in advace
Sarwan (2 Replies)
Hi,
I tried creating my version of the cat function in bash but left it and now I'm trying to make this function work, but it wouldn't.
#include <sys/param.h>
#include <sys/stat.h>
#include <locale.h>
#include <ctype.h>
#include <err.h>
#include <errno.h>
#include <fcntl.h>... (2 Replies)
I'm running one multithreaded application, in that one of my thread
is waiting infinitely in a semphore. Is there a way to determine, in
which semaphore the particular thread is waiting and which thread(s)
is holding the semaphore. (5 Replies)
Hi all,
Am using bash shell.
Am newbie, trying to understand the debugin process of a shell script...
I am unable to comprehend the control flow ,meaning from where exactly the execution of the script begins...
I tried using bash-xv <scriptname> but since am new ,am finding it difficult to... (2 Replies)
when I tried to debug my application i got the following.
gdb -v
GNU gdb 6.6
file is in C and Xmotiff Languages
(gdb) attach 25499
Attaching to process 25499
Retry #1:
Retry #2:
Retry #3:
Retry #4:
0xfea40b68 in ?? ()
(gdb) where
#0 0xfea40b68 in ?? () (0 Replies)
Hi i want to debug the C program with GDB debugger. I want to debug the program by line by line. I want to debug program like as we debug the program in Turbo-C using the F8. Can any one help me?
I know i have to use single stepping. But i don't know how to use it. Any help can be appreciated..... (5 Replies)
is there any way you can add a breakpoint in a script so you can stop on it?
i have used -xv in my shebang but the script just runs and i want it to stop at a specific point in the script.
appreciate any help. (1 Reply)
hey
i have a problem with a switch case in program and the debugger is messy has hell ( we use normal VI and gdb in our schoool to make it more diffiacult)
any way i have a problom where for some unknown reason the debugger just skips a switch statment as if it wasent even there
the rest... (2 Replies)
So here I have a simple function that I wish to debug. However, I am unable to debug the desired function even with set -o functrace enabled. Before resorting to asking this question, I had managed to find a possible solution that did not produce the desired results, which is located here.
How... (5 Replies)
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
I am VERY much a neophyte with shell scripting. I am working on the following,
1. The problem statement, all variables and given/known data:
"Create a script sends an... (7 Replies)
Discussion started by: doghouse308
7 Replies
LEARN ABOUT FREEBSD
ddb
DDB(8) BSD System Manager's Manual DDB(8)NAME
ddb -- configure DDB kernel debugger properties
SYNOPSIS
ddb capture [-M -core] [-N -system] print
ddb capture [-M -core] [-N -system] status
ddb script scriptname
ddb script scriptname=script
ddb scripts
ddb unscript scriptname
ddb pathname
DESCRIPTION
The ddb utility configures certain aspects of the ddb(4) kernel debugger from user space that are not configured at compile-time or easily
via sysctl(8) MIB entries.
To ease configuration, commands can be put in a file which is processed using ddb as shown in the last synopsis line. An absolute pathname
must be used. The file will be read line by line and applied as arguments to the ddb utility. Whitespace at the beginning of lines will be
ignored as will lines where the first non-whitespace character is '#'.
OUTPUT CAPTURE
The ddb utility can be used to extract the contents of the ddb(4) output capture buffer of the current live kernel, or from the crash dump of
a kernel on disk. The following debugger commands are available from the command line:
capture [-M core] [-N system] print
Print the current contents of the ddb(4) output capture buffer.
capture [-M core] [-N system] status
Print the current status of the ddb(4) output capture buffer.
SCRIPTING
The ddb utility can be used to configure aspects of ddb(4) scripting from user space; scripting support is described in more detail in
ddb(4). Each of the debugger commands is available from the command line:
script scriptname
Print the script named scriptname.
script scriptname=script
Define a script named scriptname. As many scripts contain characters interpreted in special ways by the shell, it is advisable to
enclose script in quotes.
scripts
List currently defined scripts.
unscript scriptname
Delete the script named scriptname.
EXIT STATUS
The ddb utility exits 0 on success, and >0 if an error occurs.
EXAMPLES
The following example defines a script that will execute when the kernel debugger is entered as a result of a break signal:
ddb script kdb.enter.break="show pcpu; bt"
The following example will delete the script:
ddb unscript kdb.enter.break
For further examples, see the ddb(4) and textdump(4) manual pages.
SEE ALSO ddb(4), textdump(4), sysctl(8)HISTORY
The ddb utility first appeared in FreeBSD 7.1.
AUTHORS
Robert N M Watson
BUGS
Ideally, ddb would not exist, as all pertinent aspects of ddb(4) could be configured directly via sysctl(8).
BSD December 24, 2008 BSD
02-25-2018
