We are testing NFS Isilon mounts with autosys jobs. We continue to receive an autosys profile not found error. We have confirmed the profile file exists and can be referenced by the ID being used.
Autosys remote agent process is able to recognized and see the command section (command to be executed after profile sets environment) but not the profile section.
Autosys log message
Isilon mount in fstab
Last edited by rbatte1; 09-11-2014 at 12:07 PM..
Reason: Added CODE tags
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)
Hi Guys..
This is Mahesh..
Actually I have to work with autosys...
Can anyone tell me how to start Autosys in the command prompt of Linux(fedora 8)?
And from where can i download autosys software (2 Replies)
Hi,
I have one autosys job that will retrieve the proccess id's and will kill those processess as follows,
pid=`/usr/ucb/ps -auwwxx | grep MAIN |nawk '{print $2}'`
kill -9 pid
but after executing this particular job, its status is showing as TE(terminated) and the kill process is... (3 Replies)
All the autosys jobs are on server-1 and server-1 has been crashed due to some reason, Now I have to run 5 autosys jobs on server-2 (failover server) which are on server 1.
How to do with Autosys command (which command needs to fired on JIL) (0 Replies)
We require Autosys remote agent to be installed in Unix (AIX) server to invoke a Unix script from Autosys.
But the issue is there is already a Jobtrac scheduler present in this server, and the support team who do Autosys installation say that these 2
schedulers cannot exist in the same server.... (0 Replies)
We require Autosys remote agent to be installed in Unix (AIX) server to invoke a Unix script from Autosys.
But the issue is there is already a Jobtrac scheduler present in this server, and the support team who do Autosys installation say that these 2
schedulers cannot exist in the same server.... (0 Replies)
We require Autosys remote agent to be installed in Unix (AIX) server to invoke a Unix script from Autosys.
But the issue is there is already a Jobtrac scheduler present in this server, and the support team who do Autosys installation say that these 2
schedulers cannot exist in the same server.... (0 Replies)
Hi Friends,
There is an Autosys scheduled job that runs on the second day of the month, and it is using the Business day calendar.
So when the month starts on a weekend or there is a holiday at the beginning of the month the second business day and second day of the month obviously do not... (1 Reply)
Discussion started by: Aditya_001
1 Replies
LEARN ABOUT OSF1
autofsd
autofsd(8) System Manager's Manual autofsd(8)NAME
autofsd, autofs - Automatically and transparently mounts and unmounts NFS file systems
SYNOPSIS
/usr/sbin/autofsd [-dv] [-D name=value]
OPTIONS
Enables debugging. When debugging is enabled, the daemon does not disassociate itself from the current tty. Messages that trace autofsd
activity are written to standard output. Logs verbose output. Defines an autofsd environment variable by assigning value to the variable.
DESCRIPTION
The autofsd daemon automatically and transparently mounts and unmounts NFS file systems on an as-needed basis. Like the automount daemon,
it provides another alternative to using the /etc/fstab file for mounting NFS file systems on client machines. However, AutoFS is more
efficient than the automount daemon because it requires less communication between the kernel and the user space daemon.
The autofsd daemon also provides higher availability than the automount daemon. Although autofsd must be running for mounts or unmounts to
be performed, if it is killed or becomes unavailable, exisiting auto-mounted NFS file systems continue to be available.
The autofsd daemon can be started from the command line or from the /sbin/rc3.d/nfs script, which reads the /etc/rc.config.common file.
Once started, it remains dormant until a user attempts to access a directory (or any file or directory in the directory hierarchy) that is
associated with an AutoFS map. The daemon then consults the appropriate map and mounts the NFS file system as specified.
AutoFS maps indicate where to find the file system to be mounted and the mount options to use. The names of the maps are passed to the aut-
ofsd daemon through the autofsmount command. For more information about AutoFS maps and the autofsmount command, see autofsmount(8) and
the Network Administration guide. Also, see sys_attrs_autofs(5) for information on tuning AutoFS.
Note
The autofsmount program reads AutoFS maps at startup. If you make any changes to the maps after startup, you must execute the autofsmount
command again to incorporate the changes.
By default, AutoFS uses UDP transport. If the tcp option is specified in a map, AutoFS attempts to use TCP. If TCP is not available, Aut-
oFS then reverts to UDP.
RESTRICTIONS
There is no support in the autofsd daemon that is analogous to the SIGTERM support in the automount command.
If a file system is locally served, the autofsd daemon creates a symbolic link on the system instead of NFS mounting the directory. If
locally serving the directory would result in a circular link, the daemon selects an external server (if available).
SEE ALSO
Commands: autofsmount(8), automount(8), mount(8)
Others: sys_attrs_autofs(5)
Network Administration
autofsd(8)