05-16-2002
Nohup command on Solaris
Hi,
I have a general question on using the "nohup" command. As far as I've got it, submmitting a job with no hang up specified, should result in the job running until completion, regardless of whether the session that submitted the job(parent) is still active. This is very helpful when doing support over a dail-in connection.
I have used this command many times on Dynix with no problems. But I have found that using it on Solaris is useless. A job will stop once the parent dies. Is this intended functionality? If so - how would you submit a job on Solaris, other than using the Crontab, if you know that the parent might die (lose connection)?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello All,
I am newbie to unix.I am trying to use NOHUP command in shell script it works fine with only "nohup test.sh 10 &" and "/opt/user/nohup test.sh 10 &" gives an error saying "ksh: /opt/user/nohup : not found".
Can anybody please guide me to make it work.
Thanks
Blazix (9 Replies)
Discussion started by: blazix
9 Replies
2. Shell Programming and Scripting
Hello, I need running the process from Oracle in backround.
Thank you for your help.
C.Abarca (1 Reply)
Discussion started by: cabarcaj
1 Replies
3. Shell Programming and Scripting
Hi
I am using nohup command in script(say nohup ls- ltr > somefile 2>&1 & ). I dont want any kind of output to be displayed on screen. When i tried the above nohup it still gives me some out put on screen like
2991
Done >somefile 2>&1
Please you let me know what is... (3 Replies)
Discussion started by: ammu
3 Replies
4. UNIX for Dummies Questions & Answers
Hello folks,
I have got a script which telnets to different boxes and runs a certain script with 3 run time args.
The line from the script which does it is:
(sleep 1; echo $USERID ; sleep 1; echo $PASSWD ; sleep 1 ; echo y ; sleep 1 ; echo "\r" ; sleep 1 ; echo "cd $FILEPATH" ; sleep 1 ; sleep 1... (1 Reply)
Discussion started by: Rajat
1 Replies
5. Shell Programming and Scripting
I want to know how to use a nohup command in the script........
I have to run following command
nohup /tmp/app/statuscheck.sh &
After typing this command I will type ctrl D to come to the prompt and the that command will run in backround.
I want to include that command in a... (2 Replies)
Discussion started by: jayaramanit
2 Replies
6. Shell Programming and Scripting
I want to know how to use a nohup command in the script........
I have to run following command
nohup /tmp/app/statuscheck.sh &
After typing this command I will type ctrl D to come to the prompt and the that command will run in backround.
Even after pressing & the command is not... (3 Replies)
Discussion started by: jayaramanit
3 Replies
7. UNIX for Dummies Questions & Answers
Hi..
Can anybody tell me, what exactly the nohup command does & when is it used?
Your help is appreciated. (3 Replies)
Discussion started by: Amol21
3 Replies
8. Shell Programming and Scripting
Hi everyone,
I am starting a nohup from a script (via scheduling system) as follows:
ssh user@server "nohup command & ; exit 0"
This command is not returning the command prompt untless I press "ENTER". This is causing the schedule to hang at this job and not continue with the rest of the jobs.... (12 Replies)
Discussion started by: nimo
12 Replies
9. AIX
I'm trying to run a compress script in the background, but I even though the script is running in the background I get "Sending nohup output to nohup.out." and the screen just stays there. How can I make the script run in background and make my command prompt come back.
I was using:
nohup... (2 Replies)
Discussion started by: NycUnxer
2 Replies
10. Solaris
Admins,
We have a strange problem on our solaris zones. We have four zones on a Global server (Sun-Fire-V890; Solaris 10 Update 6) and the SSH sessions to all four zones are terminated at a specific time (11:10 PM) every night. The SSH session to the global server is not terminated.
Also, any... (1 Reply)
Discussion started by: yogijp
1 Replies
QSTAT(1) User Contributed Perl Documentation QSTAT(1)
NAME
qstat - display job/partition information in a familiar pbs format
SYNOPSIS
qstat [-f] [-a|-i|-r] [-n [-1]] [-G|-M] [-u user_list] [-? | --help] [--man] [job_id...]
qstat -Q [-f]
qstat -q
DESCRIPTION
The qstat command displays information about jobs.
OPTIONS
-a Displays all jobs in a single-line format. See the STANDARD OUTPUT section for format details.
-i Displays information about idle jobs. This includes jobs which are queued or held.
-f Displays the full information for each selected job in a multi-line format. See the STANDARD OUTPUT section for format details.
-G Display size information in gigabytes.
-M Show size information, disk or memory in mega-words. A word is considered to be 8 bytes.
-n Displays nodes allocated to a job in addition to the basic information.
-1 In combination with -n, the -1 option puts all of the nodes on the same line as the job id.
-r Displays information about running jobs. This includes jobs which are running or suspended.
-u user_list
Display job information for all jobs owned by the specified user(s). The format of user_list is: user_name[,user_name...].
-? | --help
brief help message
--man
full documentation
STANDARD OUTPUT
Displaying Job Status
If the -a, -i, -f, -r, -u, -n, -G, and -M options are not specified, the brief single-line display format is used. The following items are
displayed on a single line, in the specified order, separated by white space:
the job id
the job name
the job owner
the cpu time used
the job state
C - Job is completed after having run E - Job is exiting after having run. H - Job is held. Q - job is queued, eligible to run or
routed. R - job is running. T - job is being moved to new location. W - job is waiting for its execution time (-a option) to be
reached. S - job is suspended.
the queue that the job is in
If the -f option is specified, the multi-line display format is used. The output for each job consists of the header line: Job Id: job
identifier followed by one line per job attribute of the form: attribute_name = value
If any of the options -a, -i, -r, -u, -n, -G or -M are specified, the normal single-line display format is used. The following items are
displayed on a single line, in the specified order, separated by white space:
the job id
the job owner
the queue the job is in
the job name
the session id (if the job is running)
the number of nodes requested by the job
the number of cpus or tasks requested by the job
the amount of memory requested by the job
either the cpu time, if specified, or wall time requested by the job, (in hh:mm)
the job state
The amount of cpu time or wall time used by the job (in hh:mm)
EXIT STATUS
On success, qstat will exit with a value of zero. On failure, qstat will exit with a value greater than zero.
perl v5.14.2 2012-04-10 QSTAT(1)