Sponsored Content
Full Discussion: Stupid question
Top Forums UNIX for Dummies Questions & Answers Stupid question Post 302217338 by jhtrice on Tuesday 22nd of July 2008 01:49:11 PM
Old 07-22-2008
ctrl+z

Elaborating a little on what reborg said..
After hitting Ctrl+z you can type bg to have the command continue in background. fg will continue the command in foreground. jobs list jobs status. kill %1 will kill job number 1.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Stupid Question?

I have a SparcStation 10 and it came with an external CD Rom Drive. I am trying to install Solaris 2.6 Server on this machine from the Cd Rom. At the OK> prompt I type "boot cdrom - browser" and I get an error: scsi device not found:error = -1 or something to that effect. Does anyone have any... (9 Replies)
Discussion started by: jskillet
9 Replies

2. UNIX for Dummies Questions & Answers

Stupid question...

Hello, I've always been around systems that ran windows in one version or another, so I'm familiar with what/when/where/drivers/etc for that. I want to build a unix box to use as a place to learn and become more familiar with unix. I would also like to eventually convert it to a server to... (6 Replies)
Discussion started by: Cortney
6 Replies

3. UNIX for Dummies Questions & Answers

sorry if this is a stupid question

Hi All, just a thought is it possible to make the shell read the following command $ $*pdf to list all pdf ($ls *.pdf) and $*htm as ($ls *.htm) Thanks for the inputs :) (2 Replies)
Discussion started by: sskb
2 Replies

4. UNIX for Dummies Questions & Answers

Stupid question

I need to convert a Unix file to a 'Dos' file. Ie if I look at the converted file in 'vi' on Unix it will have '^M' at the end of each line. Hopefully it won't be a case of reading each line in turn and adding a \n. I've heard there is some sort of unix2dos command but it is not recognised on... (2 Replies)
Discussion started by: Bab00shka
2 Replies

5. UNIX for Dummies Questions & Answers

stupid question!?

fedora core 2 xx8. 5xx version (not sure! not sure how to look it up either..(except on boot sorry!!)).. :( the linux version I started on last year was an old redhet 6.0 version with only text mode.. back then for some reason I knew I how to get rid of whole directories without a) going through... (6 Replies)
Discussion started by: moxxx68
6 Replies

6. UNIX for Dummies Questions & Answers

Sorry! Stupid question, but...

Hey everybody. I'm going through my system (Mac OS X 10.3.9, through the Terminal application) trying to get rid of instances of MySQL that I installed over each other. I was having trouble getting MySQL to work: it wasn't letting me set the password, then it wouldn't let me create new databases... (2 Replies)
Discussion started by: starscream
2 Replies

7. IP Networking

stupid IP question

Hello! I'm sorry - I know nothing about computers, but I have a dumb question. Could someone explain to me if two computers, say in a large city, could have the same IP address on different days, if they were using broadband internet? Or, is it possible an internet service provider could assign... (3 Replies)
Discussion started by: sugarsweet
3 Replies

8. UNIX for Dummies Questions & Answers

One stupid question

Has anybody come across the situation when after openning the cover of HP9000 the PC will not start. We checked everything but did not manage to find any solution to that. The PS seems to be functionning (at lease we can hear it clicking). Please help us solving the problem. Thanks to everybody. (2 Replies)
Discussion started by: Andrey Malishev
2 Replies

9. UNIX for Dummies Questions & Answers

Stupid question

Hi all, Please excuse my ignorance - I'm a Cisco kid and my knowledge of Unix is somewhat flaky!! Basically we're running MRTG on an HP-UX server and wondered what the "-" means in the following text within the crontab file - -* * * * * root /home/mrtg/fwdev01.sh I... (3 Replies)
Discussion started by: freakydancer
3 Replies

10. AIX

stupid question: the path

I'm sorry for my stupid question, but when I log in with one account on my AIX machine, I see: psar3@caixpc24: /home/psar3 > > When I login with another login (pger1), I see: caixpc24 # how can i change that i see the same for pger1 as for psar3??? (it's easy to see with which... (4 Replies)
Discussion started by: Leilah
4 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 04:16 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy