04-29-2009
Hello,
Thank you for the help.
I definitely have to get a value returned into my var from the function else I'll run into the world of globals which I wish to avoid.
I would like to know if using "kill" is actually advised or if it has any side effects as am okay with checking the return status of the function in my parent script if kill is not the good way to go.
Thank You
Regards,
HKansal
10 More Discussions You Might Find Interesting
1. Programming
How to get exit value of an executable that gets called from function?
I have an executable called “myexec” which returns 0 on success and different values for different fail scenarios.
I need to call this (myexec) executable from “myprog()” function of other executable and get the exit value... (1 Reply)
Discussion started by: sureshreddi_ps
1 Replies
2. Shell Programming and Scripting
Hi ,
I have three funcions f1, f2 and f3 .
f1 calls f2 and f2 calls f3 .
I have a global variable "period" which i want to pass to f3 .
Can i pass the variable directly in the definition of f3 ?
Pls help .
sars (4 Replies)
Discussion started by: sars
4 Replies
3. Shell Programming and Scripting
I have two scripts. script1.sh looks
--------------------------------
#!/bin/bash
display()
{
echo "Welcome to Unix"
}
display
-----------------------------
Script2.sh
#!/bin/bash
sh script1.sh //simply calling script1.sh
------------------------------ (1 Reply)
Discussion started by: mvictorvijayan
1 Replies
4. Shell Programming and Scripting
Hi all,
Am writing a script that uses the case statement and it is not working the way that I expect it to be. Script so far is as below.
What am expecting to happen is if the user enter neither Y or YES or N or NO, it is supposed to exit out of the script running only on_exit, otherwise,... (3 Replies)
Discussion started by: newbie_01
3 Replies
5. UNIX for Advanced & Expert Users
Hi Guys,
I am trying to pass arguments to the script i am wrinting.
When no argument is passed or wrong argument is passed, the script needs to output the way it needs to be called and exit.
Currently, when no arguments is passed, it is not getting exited but goes on assuming those... (3 Replies)
Discussion started by: mac4rfree
3 Replies
6. UNIX for Dummies Questions & Answers
We have a program source C and is required to indicate how many times each function is called from the C program. also print the line number where there is a call.
I've tried something like this:
#!/bin/sh
for i in $*;do
if !
then
echo $i is not a C file.
else echo $i... (0 Replies)
Discussion started by: oana06
0 Replies
7. UNIX for Dummies Questions & Answers
Hi everyone.
#!/sbin/sh
EXITING()
{
umount /FOLDER
rm -Rf /FOLDER
echo "EXIT"
exit 0
}
EXITING
echo "OK" (8 Replies)
Discussion started by: vacadepollo
8 Replies
8. Shell Programming and Scripting
I have the below script which creates a directory or simply terminates without throwing error (exit 1) incase the directory exists.
bash-4.1$ vi mdir.sh
#!/bin/bash -e
shopt -s expand_aliases
alias mkdir=mkdir_s
mkdir_s(){
if ]; then
echo " directory EXISTS "
return
else
echo "... (3 Replies)
Discussion started by: mohtashims
3 Replies
9. UNIX for Beginners Questions & Answers
Hi All,
I want to write a bash script in which a function needs to be called based on its first character in a supplied string. eg function "j" should be called when "jab" or "jgh" or "j" .... etc is hit. I have used complete -F in below script, however here function is invoked... (1 Reply)
Discussion started by: temp.sha
1 Replies
10. Shell Programming and Scripting
Hi All,
Good Day, seeking for your assistance on how to not perform my 2nd, 3rd,4th etc.. function if my 1st function is in else condition.
#Body
function1()
{
if
then
echo "exist"
else
echo "not exist"
}
#if not exist in function1 my all other function will not proceed.... (4 Replies)
Discussion started by: meister29
4 Replies
KILL(1) General Commands Manual KILL(1)
NAME
kill, broke - print commands to kill processes
SYNOPSIS
kill name
broke
DESCRIPTION
Kill prints commands that will cause all processes called name and owned by the current user to be terminated. Use the send command of
81/2(1), or pipe the output of kill into rc(1) to execute the commands.
Kill suggests sending a kill note to the process; the same message delivered to the process's ctl file (see proc(3)) is a surer, if heavy
handed, kill, but is necessary if the offending process is ignoring notes.
Broke prints commands that will cause all processes in the Broken state and owned by the current user to go away. When a process dies
because of an error caught by the system, it may linger in the Broken state to allow examination with a debugger. Executing the commands
printed by broke lets the system reclaim the resources used by the broken processes.
SOURCE
/rc/bin/kill
/rc/bin/broke
SEE ALSO
ps(1), stop(1), proc(3)
KILL(1)