04-20-2011
Fair enough. "linux 2.6.9" only tells me what kernel it uses by the way, that's no indication of what set of software is using it. What distro is it?
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
LINUX(4) BSD Kernel Interfaces Manual LINUX(4)
NAME
linux -- Linux ABI support
SYNOPSIS
To compile support for this ABI into an i386 kernel place the following line in your kernel configuration file:
options COMPAT_LINUX
for an amd64 kernel use:
options COMPAT_LINUX32
Alternatively, to load the ABI as a module at boot time, place the following line in loader.conf(5):
linux_load="YES"
DESCRIPTION
The linux module provides limited Linux ABI (application binary interface) compatibility for userland applications. The module provides the
following significant facilities:
o An image activator for correctly branded elf(5) executable images
o Special signal handling for activated images
o Linux to native system call translation
It is important to note that the Linux ABI support it not provided through an emulator. Rather, a true (albeit limited) ABI implementation
is provided.
The following sysctl(8) tunable variables are available:
compat.linux.osname Linux kernel operating system name.
compat.linux.osrelease Linux kernel operating system release. Changing this to something else is discouraged on non-development systems,
because it may change the way Linux programs work. Recent versions of GNU libc are known to use different syscalls
depending on the value of this sysctl.
compat.linux.oss_version Linux Open Sound System version.
The linux module can be linked into the kernel statically with the COMPAT_LINUX kernel configuration option or loaded as required. The fol-
lowing command will load the module if it is neither linked into the kernel nor already loaded as a module:
if ! kldstat -v | grep -E 'linux(aout|elf)' > /dev/null; then
kldload linux > /dev/null 2>&1
fi
Note that dynamically linked Linux executables will require a suitable environment in /compat/linux. Specifically, the Linux run-time
linker's hints files should be correctly initialized. For this reason, it is common to execute the following commands to prepare the system
to correctly run Linux executables:
if [ -x /compat/linux/sbin/ldconfig ]; then
/compat/linux/sbin/ldconfig -r /compat/linux
fi
For information on loading the linux kernel loadable module automatically on system startup, see rc.conf(5). This information applies
regardless of whether the linux module is statically linked into the kernel or loaded as a module.
FILES
/compat/linux minimal Linux run-time environment
/compat/linux/proc limited Linux process file system
/compat/linux/sys limited Linux system file system
SEE ALSO
brandelf(1), elf(5), linprocfs(5), linsysfs(5)
HISTORY
Linux ABI support first appeared in FreeBSD 2.1.
BSD
February 8, 2010 BSD