04-20-2011
We run Autosys here, but I'm sure it's not the conventional way. One daemon that might be in common is 'auto_remote'. Grep for this process and see if that is running.
If this is different, then I would first try to find out what user Autosys runs as. Then grep on that user and see if you can find a process that appears to be from Autosys.
Sorry about not being able to help you further. Hope that helps you though.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I am having problems running a script from AutoSys. The script runs fine when I run it manually, but errors out when run from AutoSys.
Error:
db2: not found
In the script, we are directing a query to db2.
Query1.sql 01/01/2004 | db2 +p >> sql.out 2>&1
where Query1.sql is an... (2 Replies)
Discussion started by: ramsi_ece
2 Replies
2. UNIX for Advanced & Expert Users
My project uses Autosys.
I am new to this product and I don't know where to start from.
Q1. Please provide me the link where I can get Autosys documentation
Q2. Please refer a good book on Autosys. (Beginner/Intermediate Level) (0 Replies)
Discussion started by: gram77
0 Replies
3. Shell Programming and Scripting
I am looking to get a report on autosys jobs in RUNNING state b/w certain time frame (timeA and timeB).
What I am after is the list of all the jobs that ran between AND during timeA and timeB.
Jobs within the timeframe could either:
A: STARTING --> RUNNING --> SUCCESS/FAILURE etc..
B: ... (0 Replies)
Discussion started by: rgilan01
0 Replies
4. Programming
I am looking to get a report on autosys jobs in RUNNING state b/w certain time frame (timeA and timeB).
What I am after is the list of all the jobs that ran between AND during timeA and timeB.
Jobs within the timeframe could either:
A: STARTING --> RUNNING --> SUCCESS/FAILURE etc..
B: ... (0 Replies)
Discussion started by: rgilan01
0 Replies
5. Solaris
I am looking to get a report on autosys jobs in RUNNING state b/w certain time frame (timeA and timeB).
What I am after is the list of all the jobs that ran between AND during timeA and timeB.
Jobs within the timeframe could either:
A: STARTING --> RUNNING --> SUCCESS/FAILURE etc..
B: ... (2 Replies)
Discussion started by: rgilan01
2 Replies
6. UNIX for Advanced & Expert Users
I am looking to get a report on autosys jobs in RUNNING state b/w certain time frame (timeA and timeB).
What I am after is the list of all the jobs that ran between AND during timeA and timeB.
Jobs within the timeframe could either:
A: STARTING --> RUNNING --> SUCCESS/FAILURE etc..
B: ... (1 Reply)
Discussion started by: rgilan01
1 Replies
7. UNIX for Advanced & Expert Users
Hi,
Is there a way to schedule a job in Autosys to run every 5th Day of Month without using custom calendar?
Thanks. (1 Reply)
Discussion started by: vbhatnag
1 Replies
8. UNIX for Advanced & Expert Users
Hi Experts,
I am new to Autosys. I created a Autosys box job to run at 10 AM daily. As scheduled, the job starts on time.
There is another box job inside the box. I have scheduled it to run at 11 AM but it kicks off automatically with the main job at 10 AM.
insert_job: Main-job ... (2 Replies)
Discussion started by: pk_bohra
2 Replies
9. Shell Programming and Scripting
Hi,
Is there any specific command to use to check only say Running jobs via autorep or similar command for Autosys? (0 Replies)
Discussion started by: sidnow
0 Replies
10. Shell Programming and Scripting
How can I check if "Autosys" is installed on my Linux and Solaris servers ?
I prefer Autosys instead of Crontab. (4 Replies)
Discussion started by: mohtashims
4 Replies
RENICE(8) System Manager's Manual RENICE(8)
NAME
renice - alter priority of running processes
SYNOPSIS
renice priority [ [ -p ] pid ... ] [ [ -g ] pgrp ... ] [ [ -u ] user ... ]
DESCRIPTION
Renice alters the scheduling priority of one or more running processes. The who parameters are interpreted as process ID's, process group
ID's, or user names. Renice'ing a process group causes all processes in the process group to have their scheduling priority altered.
Renice'ing a user causes all processes owned by the user to have their scheduling priority altered. By default, the processes to be
affected are specified by their process ID's. To force who parameters to be interpreted as process group ID's, a -g may be specified. To
force the who parameters to be interpreted as user names, a -u may be given. Supplying -p will reset who interpretation to be (the
default) process ID's. For example,
renice +1 987 -u daemon root -p 32
would change the priority of process ID's 987 and 32, and all processes owned by users daemon and root.
Users other than the super-user may only alter the priority of processes they own, and can only monotonically increase their ``nice value''
within the range 0 to PRIO_MAX (20). (This prevents overriding administrative fiats.) The super-user may alter the priority of any
process and set the priority to any value in the range PRIO_MIN (-20) to PRIO_MAX. Useful priorities are: 20 (the affected processes will
run only when nothing else in the system wants to), 0 (the ``base'' scheduling priority), anything negative (to make things go very fast).
FILES
/etc/passwd to map user names to user ID's
SEE ALSO
getpriority(2), setpriority(2)
BUGS
Non super-users can not increase scheduling priorities of their own processes, even if they were the ones that decreased the priorities in
the first place.
4th Berkeley Distribution November 17, 1996 RENICE(8)