Sponsored Content
Full Discussion: Nohup and background jobs
Top Forums Shell Programming and Scripting Nohup and background jobs Post 302699093 by pamu on Tuesday 11th of September 2012 06:09:12 AM
Old 09-11-2012
Quote:
Originally Posted by Uinx_addic
My Query is still not answered.

If i only use & and my terminal gets hunged. will by job will continue or will be killed.

Ex : sh my_script.sh &
I think it should be killed...
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

background jobs

Hi, i have a problem with turning a job into backgrund. When i enter this at the shell: spice -b darlington.cir -r output.raw > screenout.tmp & and then let me show the currently running jobs, i get the following output: + Suspended (tty output) spice -b darlington.cir -r output.raw >... (4 Replies)
Discussion started by: qsi
4 Replies

2. Programming

Background jobs

Hi there, I'm quite new to UNIX for programming. I have a script that does this: Shows on screen real-time results taken from phone calls and logs them in a file. However, when I start my script, I want my script to start logging in the file in the background, so I can continue working on... (1 Reply)
Discussion started by: Jeremiorama
1 Replies

3. Shell Programming and Scripting

background jobs exit status and limit the number of jobs to run

i need to execute 5 jobs at a time in background and need to get the exit status of all the jobs i wrote small script below , i'm not sure this is right way to do it.any ideas please help. $cat run_job.ksh #!/usr/bin/ksh #################################### typeset -u SCHEMA_NAME=$1 ... (1 Reply)
Discussion started by: GrepMe
1 Replies

4. UNIX for Advanced & Expert Users

Notification from Background jobs

Reposting, as it got lost during the database backup. :( Via a shell script a spawn 3 background jobs namely a, b & c. These will take different times to complete. I want to print a different message on completion of each. How can i find out when each one has completed independently. ... (19 Replies)
Discussion started by: vibhor_agarwali
19 Replies

5. UNIX for Dummies Questions & Answers

Background jobs

If I run a job in the background and logoff. Will the job continue to run or will my processes be killed ? (1 Reply)
Discussion started by: jxh461
1 Replies

6. UNIX for Advanced & Expert Users

nohup and background process

What is the difference between running a process using nohup and running a process in background ? Please explain (6 Replies)
Discussion started by: srksn
6 Replies

7. Solaris

solaris terminal sessions terminated and also nohup jobs

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

8. Programming

Background (nohup * &) SSH command block possible?

Hello, I am trying to find a way to send several sequential commands via SSH to a remote box in a single command. Thoughts so far: 1) Can I put them into a function and call the function within the ssh command? e.g. ssh <targetserver> $(functionx) No - then it calls the function in... (4 Replies)
Discussion started by: doonan_79
4 Replies

9. Shell Programming and Scripting

How to stop nohup which is working background

Please I have run a background script using nohup please tell me way to stop this. Thanks in Advance (4 Replies)
Discussion started by: mumakhij
4 Replies

10. UNIX for Dummies Questions & Answers

How do I send output of a background process to a file other than nohup.out?

I have a question. I will be running a background process using nohup and & command at end. I want to send output to a file say myprocess.out. So will this command work? nohup myprocess.ksh > myprocess.out & Thanks in advance guys !!! :) (3 Replies)
Discussion started by: vx04
3 Replies
condor_vacate_job(1)					      General Commands Manual					      condor_vacate_job(1)

Name
       condor_vacate_job vacate - jobs in the Condor queue from the hosts where they are running

Synopsis
       condor_vacate_job [-help -version]

       condor_vacate_job[-pool	centralmanagerhostname[:portnumber]-name scheddname][-addr "<a.b.c.d:port>"] [-fast] cluster... cluster.process...
       user... -constraint expression...

       condor_vacate_job[-pool centralmanagerhostname[:portnumber]-name scheddname][-addr "<a.b.c.d:port>"] [-fast] -all

Description
       condor_vacate_jobfinds one or more jobs from the Condor job queue and vacates them from the host(s) where they are currently  running.  The
       jobs remain in the job queue and return to the idle state.

       A job running under the standard universe will first produce a checkpoint and then the job will be killed. Condor will then restart the job
       somewhere else, using the checkpoint to continue from where it left off. A job running under any other universe will be sent  a	soft  kill
       signal (SIGTERM by default, or whatever is defined as the  SoftKillSig in the job ClassAd), and Condor will restart the job from the begin-
       ning somewhere else.

       If the -fastoption is used, the job(s) will be immediately killed, meaning that standard universe jobs will not be allowed  to  checkpoint,
       and the job will have to revert to the last checkpoint or start over from the beginning.

       If  the	-nameoption  is  specified, the named condor_scheddis targeted for processing. If the -addroption is used, the condor_scheddat the
       given address is targeted for processing. Otherwise, the local condor_scheddis targeted. The jobs to be vacated are identified  by  one	or
       more  job  identifiers,	as  described  below. For any given job, only the owner of the job or one of the queue super users (defined by the
       QUEUE_SUPER_USERS macro) can vacate the job.

       Using condor_vacate_jobon jobs which are not currently running has no effect.

Options
       -help

	  Display usage information

       -version

	  Display version information

       -pool centralmanagerhostname[:portnumber]

	  Specify a pool by giving the central manager's host name and an optional port number

       -name scheddname

	  Send the command to a machine identified by scheddname

       -addr <a.b.c.d:port>

	  Send the command to a machine located at "<a.b.c.d:port>"

       cluster

	  Vacate all jobs in the specified cluster

       cluster.process

	  Vacate the specific job in the cluster

       user

	  Vacate jobs belonging to specified user

       -constraint expression

	  Vacate all jobs which match the job ClassAd expression constraint

       -all

	  Vacate all the jobs in the queue

       -fast

	  Perform a fast vacate and hard kill the jobs

General Remarks
       Do not confuse condor_vacate_jobwith condor_vacate. condor_vacateis given a list of hosts to vacate, regardless of what jobs happen  to	be
       running	on  them.  Only  machine  owners  and  administrators  have  permission  to use condor_vacateto evict jobs from a given host. con-
       dor_vacate_jobis given a list of job to vacate, regardless of which hosts they happen to be running on. Only the owner of the jobs or queue
       super users have permission to use condor_vacate_job.

Examples
       To vacate job 23.0:

       % condor_vacate_job  23.0

       To vacate all jobs of a user named Mary:

       % condor_vacate_job  mary

       To vacate all standard universe jobs owned by Mary:

       % condor_vacate_job  -constraint 'JobUniverse == 1 && Owner == "mary"'

       Note that the entire constraint, including the quotation marks, must be enclosed in single quote marks for most shells.

Exit Status
       condor_vacate_jobwill exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure.

Author
       Condor Team, University of Wisconsin-Madison

Copyright
       Copyright  (C)  1990-2012  Condor  Team,  Computer  Sciences Department, University of Wisconsin-Madison, Madison, WI. All Rights Reserved.
       Licensed under the Apache License, Version 2.0.

       See the Condor Version 7.8.2 Manualor http://www.condorproject.org/licensefor additional notices. condor-admin@cs.wisc.edu

								  September 2012					      condor_vacate_job(1)
All times are GMT -4. The time now is 07:18 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy