11-25-2008
No problem. For future reference, run 'ksh -n scriptname.sh' to check your scripts for syntax errors. Same option works for bash shell too.
Cheers,
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have an ftp process using vpn, my box is receiving data hit and miss from the host system. Any tool that can be used within unix (ksh) to monitor that ftp process? (2 Replies)
Discussion started by: arkhewit
2 Replies
2. Shell Programming and Scripting
I have a shell script which runs from 7AM to 3AM every day. The script performs certain monitoring functions and if it has a problem it may need to email someone about it. The problem is that the notification process was never modified to handle running past midnight (from 23:59:59 till 3AM). ... (0 Replies)
Discussion started by: rdc69
0 Replies
3. Shell Programming and Scripting
hi all,
i would like to write the shell script to monitoring the processing, but if i passing the parameter the number of process is incorrect
how to slove it? many thx
got the correct number of process as following script:
===========================================================... (3 Replies)
Discussion started by: eric_wong_ch
3 Replies
4. Shell Programming and Scripting
hi friends,
I am trying to automate the daily monitoring process of UNIX server and it's processes. the script are below
i executed the above script using ksh -x monitortest1.sh in root login . It shows error at some lines .
1. i logged in using root ,but it... (8 Replies)
Discussion started by: rdhaprakasam
8 Replies
5. Shell Programming and Scripting
Hi All,
I have a Java application running in the background which process looks like this.
java -DMyService=Y -DWorkingDir
And I have a monitoring script which looks like this;
count_service=`ps -aef | grep MyService | wc -l`
if ; then
echo "Service_Stopped on `date`" >>... (6 Replies)
Discussion started by: swmk
6 Replies
6. Shell Programming and Scripting
Im having a bit of troble coming up with a script that does this monitors processes to see if they die, if they do die, restart the process
and write out to a log file that the process was restarted with the new PID and the date and time the new process was launched.
Any suggestions? (1 Reply)
Discussion started by: jspinal
1 Replies
7. Shell Programming and Scripting
GM everyone,
I have this script that goes to multiple servers and monitor a certain process and send the output to a file on servers1, the script looks like this
exec < server.list
while read SERVER
do
ssh $SERVER "ps -ef | grep process_name" >> /tmp/report
done
can someone help ad... (0 Replies)
Discussion started by: baders
0 Replies
8. Shell Programming and Scripting
GM everyone,
I have this script that goes to multiple servers and monitor a certain process and send the output to a file on servers1, the script looks like this
Code:
exec < server.listwhile read SERVER do ssh $SERVER "ps -ef | grep process_name" >> /tmp/reportdone
can someone help me... (2 Replies)
Discussion started by: baders
2 Replies
9. Shell Programming and Scripting
I am writing a script to kick off a process to gather logs on multiple nodes in parallel using "&". These processes create individual log files. Which I would like to filter and convert in CSV format after they are complete. I am facing following issues:
1. Monitor all Processes parallelly.... (5 Replies)
Discussion started by: shunya
5 Replies
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