09-12-2013
Yes.. If you run the script in nohup and background you can proceed to the next parameters in your while loop.
Nohup <<script>> &
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I have a menu driven script that does various tasks, I want to be able to call functions directly from within other unix scripts from my menu script. Is this possible? (12 Replies)
Discussion started by: LiquidChild
12 Replies
2. Shell Programming and Scripting
I have a script that calls several other scripts in a specified order:
# Loop over actions in specified order (STOP_ORDER or START_ORDER) and build and evaluate commands
for command in $(eval print '$'${action}_ORDER)
do
printf "`date`\tExecuting ${action}_${command} = `eval print... (1 Reply)
Discussion started by: rein
1 Replies
3. Shell Programming and Scripting
I have the following cron job in the crontab.
#! /bin/bash
25 15 * * 1-5 /export/home/svittala/scripts/scpt1.sh >/dev/null 2>&1.
The problem that I am facing is - the scpt1.sh can be executed manually. But, it is not executing through CRON. Not sure what's the issue. Any hints?. Thanks.... (5 Replies)
Discussion started by: vskr72
5 Replies
4. Solaris
Hi
I am getting some errors when i am running the shell script using the following syntax:
>abc.sh
but the same script works fine with the following syntax:
>sh abc.sh
wats the difference in both....please help
thanks in advance. (6 Replies)
Discussion started by: arpit_narula
6 Replies
5. Shell Programming and Scripting
What is the difference between calling the sub scripts of below two line.
/home/scripts/devdb.sh
. /home/scripts/devdb.sh
sh /home/scripts/devdb.sh
We are using the suse 2.0 version (4 Replies)
Discussion started by: kingganesh04
4 Replies
6. Shell Programming and Scripting
I have created a script to call 2-3 shell scripts to be execute in succession, however, it seems that after the first shell script completes, the entire script exits out.
Example:
1stJob.sh
2ndJob.sh
1st Job - FTP files from Mainframe to Unix using the following commands at the tail of... (1 Reply)
Discussion started by: CKT_newbie88
1 Replies
7. Shell Programming and Scripting
Hi,
I have written a some six scripts to move large files and re-size them. This has been done step by step, taking backup, creating the new files, merging the files, removing the temporary files created.
Since these files are around 500 MB, each step takes somewhere between 1 to 5 mins.
... (1 Reply)
Discussion started by: baanprog
1 Replies
8. Shell Programming and Scripting
I need to call 3 different shell scripts from 2 different scripts, one is a perl script and other is Shell script.
In Case -1 :
The perl script is myperlscript.pl
and the name of three shell scripts which need to be called from the perl script are a1.sh, a2.sh and a3.sh. Each shell script... (1 Reply)
Discussion started by: siba.s.nayak
1 Replies
9. Shell Programming and Scripting
Hi all, I'm wondering if you could give me some advice. I am new to scripting and am getting rather frustrated that i can get my script to call another script if certain criteria is met, via command line, but I cannot get the same script to work thru the cron jobs.
My first script monitors... (8 Replies)
Discussion started by: echoes
8 Replies
10. Shell Programming and Scripting
Hi all,
i have compiled a script as below. Basically this script is intended to call 3 other scripts, which i intend to run simultaneously.
#!/usr/bin/bash
HOMEDIR=/path/of/home
LOCKDIR=$HOMEDIR/lock
#check for LOCK
LOCKFILE=$LOCKDIR/$(basename $0 .sh).lock
if ; then
echo... (2 Replies)
Discussion started by: nms
2 Replies
NOHUP(1) BSD General Commands Manual NOHUP(1)
NAME
nohup -- invoke a command immune to hangups
SYNOPSIS
nohup utility [arg ...]
DESCRIPTION
The nohup command allows the specified utility to be protected from termination if the user should become logged out (for example, due to a
modem line or TCP/IP connection being dropped). To do this, nohup sets the SIGHUP signal(3) (``terminal line hangup'') to be ignored, then
executes utility along with any arguments.
If the standard output is a terminal, the standard output is appended to the file nohup.out in the current directory. If standard error is a
terminal, it is directed to the same place as the standard output. If the output file nohup.out cannot be created in the current directory,
nohup attempts to create the file in the user's home directory. If the file nohup.out cannot be created, either in the current directory or
the user's home directory, nohup will exit without invoking utility, with an exit value as described below.
ENVIRONMENT
The following variable is used by nohup.
HOME User's home directory.
EXIT STATUS
The nohup utility exits with one of the following values:
126 The utility was found but could not be invoked.
127 The utility could not be found or an error occurred in nohup.
Otherwise, the exit status of nohup will be that of utility.
SEE ALSO
signal(3)
STANDARDS
The nohup command is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible.
BSD
July 15, 2005 BSD