05-09-2017
The answer to your question has nothing to do with nohup; using ampersand (&) to terminate your commands causes each of those commands to be run asynchronously in the background. If you run the 1st command asynchronously, the second command is free to start running before the 1st command finishes.
This User Gave Thanks to Don Cragun For This Post:
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi All,
I am using Korn Shell HP UNIX and i am writing my scripts with filename extension as ksh or sh ..
I want to know what is the difference if i am giving ksh and sh
Other thing when we execute the shell script either we make it as executable and run directly else we give '.' or 'sh'... (2 Replies)
Discussion started by: ravi.sadani19
2 Replies
2. Web Development
:confused:
Hi All,
i am new to unix....so i am not sure whether i am asking the related question with our forum..
My question .....Can anyone explain me about the CGI script
is it something related to Unix or Linux or some other language.
Thanks in advance
Sha (1 Reply)
Discussion started by: Shahul
1 Replies
3. Shell Programming and Scripting
Hi, I am analisying an existing script. what the below code will do?
if
can some onle tell me what -a will do here. Upto my knowledge it can be used as and.
In this case they gave a comment like-- it will check for the existance of the ref file. I feel -f need to be used to check the existence.... (2 Replies)
Discussion started by: kponsms
2 Replies
4. UNIX for Dummies Questions & Answers
Hi,
I am creating two shell scripts for Database backup and the output has to be routed to nohup.out file.
We will also be running the scripts in the background as
nohup.out <script_name> &
Do I manually need to create a nohup.out file in the directory from where the scripts are going... (1 Reply)
Discussion started by: narayanv
1 Replies
5. UNIX for Advanced & Expert Users
We are facing problem while executin below script,
cat $PIPE_FILE | imscp - "${LRX_FILE_LOC}" 2>&1 | tee "${LIST_DIR}/${IMSCP_OUT_FILE}" &
sqlplus -s ${REPORTING_CONNECT} <<EOF
whenever sqlerror exit 1 rollback
spool ${PIPE_FILE}
start ${LRX_EXEC_SQL} ${LRX_MDL_RUN_DATE}
spool off
exit... (4 Replies)
Discussion started by: samiks14
4 Replies
6. UNIX for Advanced & Expert Users
Hi All,
I have a file cleanlogs_imgp01_files which has the contents as follows,
cold_log|/opt/elf/cold_spool
get_orion_log|/opt/elf/logs
get_coldFiles_log|/opt/elf/logs
get_coldFiles_TuesToSat_log|/opt/elf/logs
get_coldFiles_MonToSat_log|/opt/elf/logs
And when i execute this, I get the... (1 Reply)
Discussion started by: DevM
1 Replies
7. HP-UX
Hi,
I want to use the "SU" command in script it is asking me to enter the password manually.
pleas the say the syntax of su command in single line that includes username/password. :) (3 Replies)
Discussion started by: vigneshwaran007
3 Replies
8. UNIX for Advanced & Expert Users
Hi AM Using Unix Aix
Used
${CMD} 2> ${ERR}
Dont get what above statement works .
SCRIPT=`basename $0`
ERR=$PWD/$SCRIPT.err
DATE=`date +"%d/%m/%Y"`
CMD=2
${CMD} 2> ${ERR}
if
then
echo "SUCCESS"
else
echo "FAILURE"
fi (1 Reply)
Discussion started by: Venkatesh1
1 Replies
9. Shell Programming and Scripting
Shell : bash
OS : Oracle Linux 6.4
I want to save the ouput of a nohup command to file other than nohup.out . Below are my 3 attempts.
For both Attempt1 and Attempt2 , the redirection logs the output correctly to the output file. But I get the error "ignoring input and redirecting stderr to... (7 Replies)
Discussion started by: kraljic
7 Replies
10. Shell Programming and Scripting
what is the significance of %%.ksh in processname and %.ksh in processname_1 variable?
Why is it returning same value?How is it working?
processname=Testabc
export processname=${processname%%.ksh}
echo $processname #It is returning Testabc
export processname_1=${processname%.ksh}
echo... (2 Replies)
Discussion started by: vamsi.valiveti
2 Replies
NOHUP(1) BSD General Commands Manual NOHUP(1)
NAME
nohup -- invoke a utility immune to hangups
SYNOPSIS
nohup [--] utility [arguments]
DESCRIPTION
The nohup utility invokes utility with its arguments and at this time sets the signal SIGHUP to be ignored. If the standard output is a ter-
minal, 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.
Some shells may provide a builtin nohup command which is similar or identical to this utility. Consult the builtin(1) manual page.
ENVIRONMENT
The following variables are utilized by nohup:
HOME If the output file nohup.out cannot be created in the current directory, the nohup utility uses the directory named by HOME to create
the file.
PATH Used to locate the requested utility if the name contains no '/' characters.
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
builtin(1), csh(1), signal(3)
STANDARDS
The nohup utility is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible.
BUGS
Two or more instances of nohup can append to the same file, which makes for a confusing output.
BSD
July 19, 2001 BSD