05-05-2011
Please define "job".
You mention the "jobs" command which suggests that you may mean background jobs started by your current session.
If not, by "job" do you actually mean "process"?
What Operating System and version do you have?
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
LEARN ABOUT PHP
queuedefs
queuedefs(4) File Formats queuedefs(4)
NAME
queuedefs - queue description file for at, batch, and cron
SYNOPSIS
/etc/cron.d/queuedefs
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
q.[njobj][nicen][nwaitw]
The fields in this line are:
q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see
at(1)); c is the default queue for jobs run from a crontab(1) file.
njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100.
nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2.
nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's
queue, or because the system-wide limit of jobs executing has been reached. The default value is 60.
Lines beginning with # are comments, and are ignored.
EXAMPLES
Example 1: A sample file.
#
#
a.4j1n
b.2j2n90w
This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying
again to run it.
The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job
cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All other queues can
have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs
are running cron will wait 60 seconds before trying again to run it.
FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron.
SEE ALSO
at(1), crontab(1), nice(1), cron(1M)
SunOS 5.10 1 Mar 1994 queuedefs(4)