01-17-2004
checking for script errors
ok, i have a script which i use to search my process' for specific keywords and kill any process containing them. there is a prompt to enter a keyword for searching and another prompt for which user you want to search the process' of. i want the script to have something that if you entered a search term that is not found or a nonpresent user to return a "incorrect search terms, re-enter a keyword or user that can be found" and the prompt would pop back up. this would be instead of a bunch of "no such pid" or other kinds of error messages. that may be a little confusing but is there any way to do what im trying?
thanks, blip
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
#!/bin/ksh
sqlplus -s user/passwd@remoteserver << EOF > errors2.log
set pagesize 0 feedback off verify off heading off echo off
select directory_nm || '/' || file_nm || '|' ||venue_id || '|' || time_id from file_control;
EOF
The output of this script is;
... (2 Replies)
Discussion started by: pavan_test
2 Replies
2. Programming
Hi all,
I have created a post-C (PC) script OrdItmpopulate.pc. When I am compiling this using the “Make” command I am getting the following error. My “make” command looks like this:
make -f $ORACLE_HOME/precomp/demo/proc/demo_proc.mk build EXE=OrdItmpopulate8.exe OBJS="OrdItmpopulate8.o"... (1 Reply)
Discussion started by: musavir19
1 Replies
3. Shell Programming and Scripting
I m having trouble in a script.I need To write a script that will check for Following Errors in Logs Files,i.e files having Extension .log
The erros are
2008-01-01 15:19:11,822 ERROR - ORA-01115: IO error reading block from file 51 (block # 717090)
ORA-01110: data file 51:... (4 Replies)
Discussion started by: ali560045
4 Replies
4. Shell Programming and Scripting
Hello;
I'm trying to write a script to capture any hardware error from logs/syslog on my SUSE 10 servers so i can be notified if we have any hardware issues such a bad fan or battery, etc..
Thanks in advance for any help (2 Replies)
Discussion started by: Katkota
2 Replies
5. Shell Programming and Scripting
hey watsup guys
i am new in the shell script world. so i need help fom you guys, i have written these two codes and they both give the same errors( expr : syntax error).
Code 1 :
#! /bin/sh
# count1 appends an increment to a file 200 times
# note that a file called numbers must be... (5 Replies)
Discussion started by: surubi_abada
5 Replies
6. Shell Programming and Scripting
solution found....
Please use tags for scripts, listings, and console output (2 Replies)
Discussion started by: audiolord
2 Replies
7. UNIX for Dummies Questions & Answers
I have a simple script that processes files. Here's a simplified example of what I'm doing:
foreach t (web.*)
mv $t dnw$t:e.log
end
foreach t (card.*)
mv $t card$t:e.log
end
The problem is that sometimes there is no web.* file. In that case, I get an error "foreach: No match" and... (4 Replies)
Discussion started by: software5723
4 Replies
8. Shell Programming and Scripting
#!/bin/ksh
number1="20"
if
then
number1=$1
fi
number2="1"
while ]
do
if ]
then
print "FizzBuzz"
elif ]
then
print "Fizz"
elif ]
then
... (3 Replies)
Discussion started by: bjhum33
3 Replies
9. Shell Programming and Scripting
Hi,
I want to write a script which continuously checking status of a script running in background by nohup command. And if same script is not running then immediately start the script...please help..
i am using below command to run script
nohup system_traps.sh &
but in some... (9 Replies)
Discussion started by: ketanraut
9 Replies
10. 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
scotty(1) Tnm Tcl Extension scotty(1)
__________________________________________________________________________________________________________________________________________________
NAME
scotty - A Tcl shell including the Tnm extensions.
SYNOPSIS
scotty ?fileName arg arg ...?
_________________________________________________________________
DESCRIPTION
scotty is a Tcl interpreter with extensions to obtain status and configuration information about TCP/IP networks. After startup, scotty
evaluates the commands stored in .scottyrc and .tclshrc in the home directory of the user.
SCRIPT FILES
If scotty is invoked with arguments then the first argument is the name of a script file and any additional arguments are made available to
the script as variables (see below). Instead of reading commands from standard input scotty will read Tcl commands from the named file;
scotty will exit when it reaches the end of the file.
If you create a Tcl script in a file whose first line is
#!/usr/local/bin/scotty2.1.11
then you can invoke the script file directly from your shell if you mark the file as executable. This assumes that scotty has been
installed in the default location in /usr/local/bin; if it's installed somewhere else then you'll have to modify the above line to match.
Many UNIX systems do not allow the #! line to exceed about 30 characters in length, so be sure that the scotty executable can be accessed
with a short file name.
An even better approach is to start your script files with the following three lines:
#!/bin/sh
# the next line restarts using scotty
exec scotty2.1.11 "$0" "$@"
This approach has three advantages over the approach in the previous paragraph. First, the location of the scotty binary doesn't have to
be hard-wired into the script: it can be anywhere in your shell search path. Second, it gets around the 30-character file name limit in
the previous approach. Third, this approach will work even if scotty is itself a shell script (this is done on some systems in order to
handle multiple architectures or operating systems: the scotty script selects one of several binaries to run). The three lines cause both
sh and scotty to process the script, but the exec is only executed by sh. sh processes the script first; it treats the second line as a
comment and executes the third line. The exec statement cause the shell to stop processing and instead to start up scotty to reprocess the
entire script. When scotty starts up, it treats all three lines as comments, since the backslash at the end of the second line causes the
third line to be treated as part of the comment on the second line.
VARIABLES
Scotty sets the following Tcl variables:
argc Contains a count of the number of arg arguments (0 if none), not including the name of the script file.
argv Contains a Tcl list whose elements are the arg arguments, in order, or an empty string if there are no arg arguments.
argv0 Contains fileName if it was specified. Otherwise, contains the name by which scotty was invoked.
tcl_interactive Contains 1 if scotty is running interactively (no fileName was specified and standard input is a terminal-like device), 0
otherwise.
PROMPTS
When scotty is invoked interactively it normally prompts for each command with ``% ''. You can change the prompt by setting the variables
tcl_prompt1 and tcl_prompt2. If variable tcl_prompt1 exists then it must consist of a Tcl script to output a prompt; instead of out-
putting a prompt scotty will evaluate the script in tcl_prompt1. The variable tcl_prompt2 is used in a similar way when a newline is typed
but the current command isn't yet complete; if tcl_prompt2 isn't set then no prompt is output for incomplete commands.
SEE ALSO
Tnm(n), Tcl(n)
AUTHORS
Juergen Schoenwaelder <schoenw@cs.utwente.nl>
Tnm scotty(1)