04-20-2011
Linux is not an entire operating system complete with services and applications. Linux is a 4-megabyte kernel file which is loaded on boot, and maybe a few modules. Absolutely everything else is the distribution(redhat, fedora, SuSE, mandriva, gentoo, ...)
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 DEBIAN
socklog-check
socklog-check(8) System Manager's Manual socklog-check(8)
NAME
socklog-check - checks for the availability of a socklog(8) service.
SYNOPSIS
socklog-check [-v] [unix [address]]
DESCRIPTION
socklog-check attempts to connect to a socklog(8) unix service and reports whether the connection attempt succeeded or not.
It connects to the datagram oriented unix domain socket address, and reports success through the return code. If address is not specified,
socklog-check attempts to connect to /dev/log.
When running services that use the syslog facility under runit's service supervision, socklog-check should be added to the top of the ser-
vice's run script to ensure that no syslog messages are generated until a syslog service is up and running to process the messages, e.g.:
#!/bin/sh
socklog-check || exit 1
exec service_using_syslog
OPTIONS
-v verbose. Print verbose message to standard error.
EXIT CODES
On success socklog-check returns 0.
On error, socklog-check prints a message to standard error and exits 111.
SEE ALSO
socklog(8), socklog-conf(8), svlogd(8), tryto(1), uncat(1), sv(8), runsv(8), runsvdir(8)
http://smarden.org/socklog/
http://smarden.org/runit/
AUTHOR
Gerrit Pape <pape@smarden.org>
socklog-check(8)