Run command in background thru script Post: 302588421

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

how to run script at background

Hi all, I have a script like: echo Please input list file name: read listn for file in `cat $listn.txt` do send_file $file done normally, I will run the script like: :. resendfile Please input list filename: list1 #Then, the script will resend all file from the list1. However,...

2. Shell Programming and Scripting

set schedule to run a script at background while logout

Hi, How can I run a script at 9:00am and 6:00pm everyday? Can I run it at background while I logout my account? Please help!! Many Thanks!!

3. Shell Programming and Scripting

Is there away to run script in background within the script

Hello all i have csh script called test.csh , and i need to run it in the background so i do : test.csh & but i wander can i tell within the script source to run it in the background automatically , without giving the user to add the "&" when executing in the shell ?

4. Solaris

Best practice to run bash script in background

nohup /bin/bassh $HOME/scripts/test.sh > $HOME/log/test.log 2>&1 & nohup $HOME/scripts/test.sh > $HOME/log/test.log 2>&1 & Which is the good practice to run a script in background of above two ? does the first one will have any overhead on the system ? our system is SunOS 5.10...

5. UNIX for Dummies Questions & Answers

Run script in the background with a time interval

I have a script I want to run in the background, and I have looked it up but I am not exactly sure how to do. First of all to run it in the background do you have to put something in the script or is it just a command when you go to run it. I found this solution to it but once again I am not to...

6. Shell Programming and Scripting

shell script does not work if run in background

Dear All, I am trying to run a script in background like ./scriptname.sh & but when i try to run it in background it is giving me an error "syntax error at line 12: `(' unexpected" at the line 12, there is a function definition "function getFileList()". This script runs fine if i run on...

7. Shell Programming and Scripting

Need to run the script in background, but having a problem

hi, we have a script which runs for the whole day and whenever the job fails, will send an alert to the mailbox. My problem here is that i need to give the jobname dynamically which is not possible if we run the script in background. Pls help me with this. Thanks Ajay

8. Shell Programming and Scripting

Need help! command working ok when executed in command line, but fails when run inside a script!

Hi everyone, when executing this command in unix: echo "WM7 Fatal Alerts:", $(cat query1.txt) > a.csvIt works fine, but running this command in a shell script gives an error saying that there's a syntax error. here is content of my script: tdbsrvr$ vi hc.sh "hc.sh" 22 lines, 509...

9. Shell Programming and Scripting

Script for telnet and run one command kill it and run another command using while loop

( sleep 3 echo ${LOGIN} sleep 2 echo ${PSWD} sleep 2 while read line do echo "$line" PID=$? sleep 2 kill -9 $PID done < temp sleep 5 echo "exit" ) | telnet ${HOST} while is executing only command and exits.

10. UNIX for Beginners Questions & Answers

How to run a shell script in background without showing in the terminal?

Hi Guys, i am having a script which checks for ip address is pingable or not,when i execute this script in terminal it keeps on showing the pinging status of every ip address and it takes more time when i check for 100 ip address,How to do run a script in background without showing in the terminal...

LEARN ABOUT BSD

kill

KILL(1) 						      General Commands Manual							   KILL(1)

NAME

       kill - terminate a process with extreme prejudice

SYNOPSIS

       kill [ -sig ] processid ...
       kill -l

DESCRIPTION

       Kill  sends the TERM (terminate, 15) signal to the specified processes.	If a signal name or number preceded by `-' is given as first argu-
       ment, that signal is sent instead of terminate (see sigvec(2)).	 The  signal  names  are  listed  by  `kill  -l',  and	are  as  given	in
       /usr/include/signal.h, stripped of the common SIG prefix.

       The  terminate  signal  will  kill  processes  that do not catch the signal; `kill -9 ...' is a sure kill, as the KILL (9) signal cannot be
       caught.	By convention, if process number 0 is specified, all members in the process group  (i.e.  processes  resulting	from  the  current
       login)  are  signaled  (but  beware:  this works only if you use sh(1); not if you use csh(1).)	Negative process numbers also have special
       meanings; see kill(2) for details.

       The killed processes must belong to the current user unless he is the super-user.

       The process number of an asynchronous process started with `&' is reported by the shell.  Process numbers can also be found by using ps(1).
       Kill  is  a  built-in  to  csh(1); it allows job specifiers of the form ``%...'' as arguments so process id's are not as often used as kill
       arguments.  See csh(1) for details.

SEE ALSO

       csh(1), ps(1), kill(2), sigvec(2)

BUGS

       A replacement for ``kill 0'' for csh(1) users should be provided.

4th Berkeley Distribution					  April 20, 1986							   KILL(1)