05-04-2011
ok I know that I can display all running processes with ps -ux. I can display only the processes that I am running by ps -U citizencro. I can kill what process I want with with kill -9 %pid and it will display that it was killed. I don't get how I can pipe the two together where it asks me out of my jobs which one do I want to kill, then kills and confirms it?
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I have a small problem. It's annoying though. I wrote this shell script:
#
# This script will accept two arguments. The first is a flag and the
# second is a time interval. The only valid flag is '-t' which means
# the user will specify the interval in seconds, otherwise the
# default is 600... (3 Replies)
Discussion started by: el_toro
3 Replies
2. Shell Programming and Scripting
Hi,
Thanks in advance.
i need to kill a unix background running job after that job process completes.
i can kill a job by giving the following unix command
kill -9 processid
how to kill the job after the current process run gets completed ?
Appreciate your valuable help.
... (1 Reply)
Discussion started by: dtazv
1 Replies
3. Shell Programming and Scripting
Hi!
I'm using a script to start a process that might run forever if some parameters are given wrong (it's part of an optimization). I would now like to have the process killed after a certain walltime in that case. So far I get it done with the following lines
./My_process.e &
pid=`ps -ef |... (3 Replies)
Discussion started by: ciwstevie
3 Replies
4. Solaris
Hi,
Thanks in advance.
i need to kill a unix background running job after that job process completes.
i can kill a job by giving the following unix command
kill -9 processid
how to kill the job after the current process run gets completed ?
Appreciate your valuable help.
Thanks... (7 Replies)
Discussion started by: dtazv
7 Replies
5. UNIX for Dummies Questions & Answers
Hi everyone:
I'm trying to make a CRON job that will execute Fridays at 7am. I have the following:
* 7 * * 5
I've been studying up on CRON and I know to have this in a file and then "crontab filename.txt" to add it to the CRON job list.
The CRON part I believe I understand, but I would... (6 Replies)
Discussion started by: Annorax
6 Replies
6. Shell Programming and Scripting
Hi,
If I have a large shell script running as root, say for example like one that copies a ton of files, how would I kill the shell script and any processes that it created?
Thanks (7 Replies)
Discussion started by: pcwiz
7 Replies
7. Shell Programming and Scripting
Job ad removed (1 Reply)
Discussion started by: starmation
1 Replies
8. Shell Programming and Scripting
Hi Gurus,
I have a test unix server in which currently some unix cronjob are running.
I have written two script one is a shell script in which env variable are there (in that i am exporting those variables).
I have also written a perl script .
when i am running at the shell manually like... (5 Replies)
Discussion started by: sanjay.login
5 Replies
9. UNIX for Advanced & Expert Users
Hi,
I have one autosys job that will retrieve the proccess id's and will kill those processess as follows,
pid=`/usr/ucb/ps -auwwxx | grep MAIN |nawk '{print $2}'`
kill -9 pid
but after executing this particular job, its status is showing as TE(terminated) and the kill process is... (3 Replies)
Discussion started by: Kattoor
3 Replies
10. UNIX for Dummies Questions & Answers
Hi,
I'm executing a python script via cron job. The way it is set up is, I'm editing a file called local00 22 * * * root su - -c "/opt/setup_dir/bin/run_bkp -p"
When this job executes, the command-specific logfile and the syslog (where the logs are supposed to go) show half of the logs(no... (2 Replies)
Discussion started by: ashwini.engr07
2 Replies
fg(1) General Commands Manual fg(1)
NAME
fg - Runs jobs in the foreground
SYNOPSIS
fg [job_id...]
Note
The C shell has a built-in version of the fg command. If you are using the C shell, and want to guarantee that you are using the command
described here, you must specify the full path /usr/bin/fg. See the csh(1) reference page for a description of the built-in command.
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
fg: XCU5.0
Refer to the standards(5) reference page for more information about industry standards and associated tags.
OPTIONS
None
OPERANDS
Specifies the job to be run as a foreground job. If no job_id operand is given, the job_id for the job that was most recently suspended,
placed in the background or run as a background job is used. The format of job_id is described in the Jobs section of the ksh(1) reference
page.
DESCRIPTION
If job control is enabled (see the description of set -m in the ksh(1) reference page), the fg utility moves a background job from the cur-
rent environment into the foreground.
Using fg to place a job into the foreground removes its process ID from the list of those "known in the current shell execution environ-
ment"; see the Jobs section of the ksh(1) reference page.
RESTRICTIONS
If job control is disabled, the fg utility exits with an error and no job is placed in the foreground. The fg utility does not work as
expected when it is operating in its own utility execution environment because that environment has no applicable jobs to manipulate.
EXIT STATUS
The following exit values are returned: Successful completion. An error occurred.
ENVIRONMENT VARIABLES
The following environment variables affect the execution of fg: Provides a default value for the internationalization variables that are
unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization vari-
ables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string value,
overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of bytes
of text data as characters (for example, single-byte as opposed to multibyte characters in arguments). Determines the locale used to
affect the format and contents of diagnostic messages written to standard error. Determines the location of message catalogues for the
processing of LC_MESSAGES.
SEE ALSO
Commands: bg(1), csh(1), jobs(1), kill(1), ksh(1), sh(1p), wait(1)
Standards: standards(5)
fg(1)