10-09-2013
You can use $! to get the PID of the last started background process.
You can also use jobs %1 to get the status of the job (testing it with $?), and kill %1 to kill it.
This User Gave Thanks to Scott For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hiya,
Recently I've run a few scripts in the foreground, but have realised later they should of been better nohup'd and placed in the background. I understand how to change a foreground job into a background one, but how would put the job into the nohup state?
Thanks (1 Reply)
Discussion started by: rdbooth
1 Replies
2. Shell Programming and Scripting
Hi all,
I am running a job .. and i want to know the status tht it is runnig or not ..
and how can i find the jobId of my job ..
I have to get it to kill my running job
Pls let me know da Unix commands to do it ..
i m wrking on Hp UNIX (1 Reply)
Discussion started by: ravi.sadani19
1 Replies
3. Shell Programming and Scripting
I have run one shell script in background that contains a endless while loop.
I am not able to know the status of that job .
Please provide any command to know this. I have already used "ps -aef" , "jobs" to know it , but it didn't work. I am sure the process is running as it is generating a file... (8 Replies)
Discussion started by: sumanta
8 Replies
4. AIX
Guys,
We use AIX 5.3 at our work place. I only in my team have a strange problem of not able run jobs background. Other colleagues are able to run without any problem.
Once I kick off background job using nohup and & command, It immediately stops. The following error I get when I run.
... (2 Replies)
Discussion started by: anandsbr
2 Replies
5. UNIX for Dummies Questions & Answers
Hello,
I am running a shell script whose execution often takes several hours to complete. Is there way I can get some kind of status update as the job is running? Something as simple as the start and the current time stamp.
Thanks,
Gussi (2 Replies)
Discussion started by: Gussifinknottle
2 Replies
6. Shell Programming and Scripting
Hi All,
I have a scenario where I am executing some child shell scripts in background (using &)through a master parent script.
Is there a way I can capture the exit status of each individual child script after the execution is completed. (2 Replies)
Discussion started by: paragkalra
2 Replies
7. UNIX for Dummies Questions & Answers
Is there a way to suspend (TSTP?) a job that is running in the background, _without_ first bringing it to the foreground and inputting Ctrl-Z from the keyboard?
IOW, something similar to issuing the shell's bg builtin command on a job ID to resume a job that is suspended in the background,... (2 Replies)
Discussion started by: uiop44
2 Replies
8. Shell Programming and Scripting
Hello Everyody,
Having a doubt.
sort file1 &
when we sent a job to the background it returns
Job Number
PID
again if we want to ... (1 Reply)
Discussion started by: knroy10
1 Replies
9. Solaris
Hi,
Should the user jobs specified in crontab be running in background?
Cron daemon is already running in background. So I am not sure
whether should the jobs (output and error messages are redirected to file)
ran by it be explicitly stated to be run in background (& at end of command)
if one... (1 Reply)
Discussion started by: joe_x
1 Replies
10. Shell Programming and Scripting
Hi,
I want to write a script which continuously checking status of a script running in background by nohup command. And if same script is not running then immediately start the script...please help..
i am using below command to run script
nohup system_traps.sh &
but in some... (9 Replies)
Discussion started by: ketanraut
9 Replies
LEARN ABOUT SUSE
vm-install-jobs
vm-install-jobs(8) System Manager's Manual vm-install-jobs(8)
NAME
vm-install-jobs - queries and manages VM creation jobs that were started by vm-install
SYNOPSIS
vm-install-jobs [options ...]
DESCRIPTION
VMs may be created by vm-install interactively, or as backgrounded jobs. The vm-install-jobs command manages backgrounded VM creation
jobs.
OPTIONS
--cancel job-id
Cancels the specified job. If the VM is still running, it is stopped. This command may return before the VM is completely stopped
or the vm-install process has completely exited. The job is not implicitly deleted, so that the cancelation progress may be
observed.
--delete job-id
Deletes the specified job. The job must be in one of the FINISHED, FAILED, or CANCELED states. The VM's configuration is deleted,
as are any disks that were created during the job.
--detach job-id
Detaches the created VM from the specified job. The job must be in the FINISHED state. The job is deleted, but the VM's configura-
tion and its disks are left intact.
--list Lists all known VM creation jobs, by ID. One job ID is output per line.
--status job-id
Outputs the status of the specified job.
JOB STATES
Every job is always in one of the following states:
0: SETTINGS
1: PREP_INSTALL
2: INSTALL
3: POST_INSTALL
4: RUNTIME_CONF
5: RUNTIME
6: FINISHED
7: FAILED
8: CANCELED
The normal progression is from state 0 to state 6. States 6, 7, and 8 are terminal states.
JOB STATUS
Querying the job status will print (to stdout) a number of key/value pairs. The possible keys and their meanings are:
exit The exit code of the VM creation job. This key is only present once the job is in one of the states FINISHED, FAILED, or CANCELED.
To interpret the meaning of the exit code, see vm-install(8)
id The job ID. Always present.
inotify
A filename to monitor (via inotify(7) ) for state changes. The recommended inotify mask to use is IN_CLOSE_WRITE. Always present.
log The location of the log file. Always present.
pid The process ID of the VM creation job. This key is only present if the VM creation process is still running. The PID is used
internally to cancel the job.
state The job's current state. See JOB STATES. Always present.
uuid The VM's UUID. This key is only present once all of the VM's settings have been gathered.
vnc The last known location to view the VM's console via VNC. Note that the presence of this key does not guarantee that the VM is cur-
rently running. When no authentication is necessary, the URL will be ip::port. If authentication is necessary, the URL will be
username:password@ip::port.
DIAGNOSTICS
A zero exit code indicates success; non-zero indicates failure.
Note that the exit code of this tool indicates the success of the job management command. It does not represent the success or failure of
the job itself.
SEE ALSO
To interpret the exit code of a job or of this command, see vm-install(8)
To monitor state changes of jobs, see inotify(7)
To report problems with this software or its documentation, visit http://bugzilla.novell.com
2007-02-01 vm-install-jobs(8)