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
LEARN ABOUT FREEBSD
daemon
DAEMON(8) BSD System Manager's Manual DAEMON(8)
NAME
daemon -- run detached from the controlling terminal
SYNOPSIS
daemon [-cfr] [-p child_pidfile] [-P supervisor_pidfile] [-u user] command arguments ...
DESCRIPTION
The daemon utility detaches itself from the controlling terminal and executes the program specified by its arguments. Privileges may be low-
ered to the specified user.
The options are as follows:
-c Change the current working directory to the root (``/'').
-f Redirect standard input, standard output and standard error to /dev/null.
-p child_pidfile
Write the ID of the created process into the child_pidfile using the pidfile(3) functionality. The program is executed in a spawned
child process while the daemon waits until it terminates to keep the child_pidfile locked and removes it after the process exits.
The child_pidfile owner is the user who runs the daemon regardless of whether the -u option is used or not.
-P supervisor_pidfile
Write the ID of the daemon process into the supervisor_pidfile using the pidfile(3) functionality. The program is executed in a
spawned child process while the daemon waits until it terminates to keep the supervisor_pidfile locked and removes it after the
process exits. The supervisor_pidfile owner is the user who runs the daemon regardless of whether the -u option is used or not.
-r Supervise and restart the program if it has been terminated.
-u user
Login name of the user to execute the program under. Requires adequate superuser privileges.
If the -p, -P or -r option is specified the program is executed in a spawned child process. The daemon waits until it terminates to keep the
pid file(s) locked and removes them after the process exits or restarts the program. In this case if the monitoring daemon receives software
termination signal (SIGTERM) it forwards it to the spawned process. Normally it will cause the child to exit, remove the pidfile(s) and then
terminate.
The -P option is useful combined with the -r option as supervisor_pidfile contains the ID of the supervisor not the child. This is especially
important if you use -r in an rc script as the -p option will give you the child's ID to signal when you attempt to stop the service, causing
daemon to restart the child.
EXIT STATUS
The daemon utility exits 1 if an error is returned by the daemon(3) library routine, 2 if child_pidfile or supervisor_pidfile is requested,
but cannot be opened, 3 if process is already running (pidfile exists and is locked), otherwise 0.
DIAGNOSTICS
If the command cannot be executed, an error message is displayed on standard error unless the -f flag is specified.
SEE ALSO
setregid(2), setreuid(2), daemon(3), exec(3), pidfile(3), termios(4), tty(4)
HISTORY
The daemon utility first appeared in FreeBSD 4.7.
BSD
September 13, 2013 BSD