02-20-2013
Hi Vikram,
happy to see the reply from u .... will this work even for autosys job also
10 More Discussions You Might Find Interesting
1. 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
2. HP-UX
Hi,
I have a cron schedule like this
04,16,28,40,52 * * * * /nag/startProcessABatch (unix script)
i want to add new lines in this file (like Logging), i just copy this file into a /tmp folder (for backup copy), and i have edited this file (added few lines of code for logging).
... (1 Reply)
Discussion started by: nag_sundaram
1 Replies
3. Shell Programming and Scripting
Hi, unixers, I'm doing something like
find -type f -name '*.gif' | xargs rm &
find -type f -user root | xargs chown idealo &
wait
#do more stuff
on a very large dir. I'm thinking this would be more efficient if it was running as a single process that did one thing for the first condition,... (1 Reply)
Discussion started by: tphyahoo
1 Replies
4. UNIX for Advanced & Expert Users
hi,
i have the following line in the crontab
15 5 * * 6 /home/adw/BCE_ADW.pl
The problem is the cron job is not getting started automatically.
But this was working til last week. now it is not working.
what could be the problem. Any idea? (3 Replies)
Discussion started by: Suguna
3 Replies
5. UNIX for Advanced & Expert Users
I run a job, before completion of that job, another one started the same job in the middle of running the same job. What will happen? (6 Replies)
Discussion started by: rajesh08
6 Replies
6. UNIX for Dummies Questions & Answers
Hi all,
down here part of the scheduled job in crontab (AIX Version 5)
i have problem running jspPRE-ALL.
i verrify permissions and privileges (the others job are working good)
if i run the job in command line it work correctly
#
# Aggiornamento doni e continuity
00 02 * * 2-6... (5 Replies)
Discussion started by: ilpasta
5 Replies
7. UNIX for Dummies Questions & Answers
Hi All,
I am editing crontab using -e option to add a new job
Below is the line
30 * * * * scriptpath
This job is not executing every thirty minutes.
I have checked, cron daemon is running.
What did I miss? Can some one help?
I am using cron shell..ksh (7 Replies)
Discussion started by: yabhi_22
7 Replies
8. Shell Programming and Scripting
Hi,
I have an autosys box job and 2 command jobs. When i force start the box job the command jobs are moving to 'Active' state but are not running. I have tried various options for the start times and run windows but doesnt seem to work. Any help is appreciated
update_job: job1.jil... (1 Reply)
Discussion started by: userscript
1 Replies
9. Solaris
Hi,
I have set up the crontab as follows.
root@IDC4VASAPP07 # crontab -l
0-59 * * * * /var/tmp/r.sh
0-59 * * * * date >> /var/tmp/log
root@IDC4VASAPP07 #
r.sh is as follows.
root@IDC4VASAPP07 # cat r.sh
#!/bin/bash
dt1=$(perl -e 'use POSIX;print strftime... (10 Replies)
Discussion started by: SunilB2011
10 Replies
10. Shell Programming and Scripting
Hi All,
I am writing a script that will eventually be executed by a cron job every 15 minutes. I want to make sure that my logic/script doesn't get executed if a previous job is still running. What would be the best way to handle that scenario? I was thinking to make my script create a temporary... (1 Reply)
Discussion started by: rdogadin
1 Replies
LEARN ABOUT DEBIAN
globus-fork-starter
GLOBUS-FORK-STARTE(8) University of Chicago GLOBUS-FORK-STARTE(8)
NAME
globus-fork-starter - Start and monitor a fork job
SYNOPSIS
globus-fork-starter
DESCRIPTION
The globus-fork-starter program is executes jobs specified on its standard input stream, recording the job state changes to a file defined
in the $GLOBUS_LOCATION/etc/globus-fork.conf configuration file. It runs until its standard input stream is closed and all jobs it is
managing have terminated. The log generated by this program can be used by the SEG to provide job state changes and exit codes to the GRAM
service. The globus-fork-starter program is typically started by the fork GRAM module.
The globus-fork-starter program expects its input to be a series of task definitions, separated by the newline character, each representing
a separate job. Each task definition contains a number of fields, separated by the colon character. The first field is always the literal
string 100 indicating the message format, the second field is a unique job tag that will be distinguish the reply from this program when
multiple jobs are submitted. The rest of fields contain attribute bindings. The supported attributes are:
directory
Working directory of the job
environment
Comma-separated list of strings defining environment variables. The form of these strings is var=value
count
Number of processes to start
executable
Full path to the executable to run
arguments
Comma-separated list of command-line arguments for the job
stdin
Full path to a file containing the input of the job
stdout
Full path to a file to write the output of the job to
stderr
Full path to a file to write the error stream of the job
Within each field, the following characters may be escaped by preceding them with the backslash character:
o backslash ()
o semicolor (;)
o comma (,)
o equal (=)
Additionally, newline can be represented within a field by using the escape sequence
.
For each job the globus-fork-starter processes, it replies by writing a single line to standard output. The replies again consist of a
number of fields separated by the semicolon character.
For a successful job start, the first field of the reply is the literal 101, the second field is the tag from the input, and the third
field is a comma-separated list of SEG job identifiers which consist the concatenation of a UUID and a process id. The globus-fork-starter
program will write state changes to the SEG log using these job identifiers.
For a failure, the first field of the reply is the literal 102, the second field is the tag from the input, the third field is the integer
representation of a GRAM erorr code, and the fourth field is an string explaining the error.
ENVIRONMENT
If the following variables affect the execution of globus-fork-starter
GLOBUS_LOCATION
Path to Globus Toolkit installation. This is used to locate the globus-fork.conf configuration file.
FILES
$GLOBUS_LOCATION/etc/globus-fork.conf
Path to fork SEG configuration file.
University of Chicago 12/01/2009 GLOBUS-FORK-STARTE(8)