Autosys Config file update on a read-only filer

 
Thread Tools Search this Thread
Special Forums UNIX and Linux Applications Autosys Config file update on a read-only filer
# 1  
Old 03-11-2010
Autosys Config file update on a read-only filer

Hi To All Genius out there,

We are running autosys application on solaris 10. In autosys we have a configuration file that contains an Autosys instance configuration data and is located on a NFS filer on which we have a read-only access.

Our Autosys environment is on a dual server mode(Active & Passive). Now in case of a primary server failure the secondary server takes over and before that the config file has to be updated with the Shadow server as the primary.

The twist is here, as the config file is on a read-only NFS filer and can only be updated using Clearcase utility so we need to have fix for this so that the config file is updated and the security mechanism (Clearcase) is also not overridden.

Any Help on this issue will be highly appreciated.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Update config file using shell script in Solaris 5.10

hi I need to update the value in config.txt value using shell script example: lets say a value in config.txt file is as SEQUENCE=1 after some iteration as the loop ends , the SEQUENCE should get update in the config.txt file with a new value of SEQUENCE=2. also , can anyone please help me... (7 Replies)
Discussion started by: ravidwivedi2288
7 Replies

2. Shell Programming and Scripting

Script to detect dynamic ip change and update to config file

Hi All, I am newbie here and request your assistance. I have a service running on public ip, but since I have a dynamic IP it keeps on changing and every time I need to manually get the new ip and add to the config file and restart the service. This has become bit time consuming. Hence, I... (4 Replies)
Discussion started by: Shaan_Shaan
4 Replies

3. Shell Programming and Scripting

Read Data from Config file using Perl

Hi All, Can anyone please explain me how to read data from config file in Perl. Suppose i have a config file named cfile. The data in config file is name=parth lname=mittal user=2007 hostname=fluoride username=parthmittal password=XXXXXX account=unix url=www.unix.com ... (2 Replies)
Discussion started by: parthmittal2007
2 Replies

4. Shell Programming and Scripting

Read from config file and use it in perl program

Hi, I want to configure some values in config file like below work_dir /home/work csv_dir /home/csv sql_dir /home/sqls reportfirst yes and i want to store each value in variable to use it further in my my perl program ?? any thought on this(i am new to perl) ? ... (2 Replies)
Discussion started by: raghavendra.nsn
2 Replies

5. Shell Programming and Scripting

how to read the variable indivdually from config file

how to read the variable indivdually ( line by line ) in shell script eg : i have the config file where contain cat /home/user01/ilap/conf/input.conf node.txt node2.txt node3.txt i need to run script like /home/user01/ilap/exe/run.sh /home/user01/ilap/conf/input.conf ... (1 Reply)
Discussion started by: mail2sant
1 Replies

6. Programming

Read arguments from a config file in C

Hello everybody, I'm coding a program in C and i'm getting troubles with this. I need to read a config file and store the arguments into individual variables, let's say the config file looks like the following: #This is the configuration file... 192.168.0.1 A1:B1:C1:D1:E1:F1 192.168.0.2... (2 Replies)
Discussion started by: semash!
2 Replies

7. Solaris

Autosys Config file update on a read-only filer

Hi To All Genius out there, We are running autosys application on solaris 10. In autosys we have a configuration file that contains an Autosys instance configuration data and is located on a NFS filer on which we have a read-only access. Our Autosys environment is on a dual server mode(Active... (0 Replies)
Discussion started by: whn_chips_r_dwn
0 Replies

8. Shell Programming and Scripting

Read from a config file.

Hello All, I have a config file which has the following data : export DBCHECKSUM001="/home/srvcdesk/DBCheckSum/DBCheckSum001.cfg" export DBCHECKSUM002="/home/srvcdesk/DBCheckSum/DBCheckSum002.cfg" export DBCHECKSUM003="/home/srvcdesk/DBCheckSum/DBCheckSum003.cfg" export... (1 Reply)
Discussion started by: Veenak15
1 Replies

9. Shell Programming and Scripting

how to read the variable from config file

how to read the variable from config file eg: a.cfg below config file config file which contain a=`hostname` b=250 a.sh is shell script echo "$a and $b" if i run "a.sh 1.cfg" it works but when i declare N number of variable it wont works.. can u please suggest for that ? (1 Reply)
Discussion started by: mail2sant
1 Replies

10. UNIX for Dummies Questions & Answers

How to Read a config file and Assign to Variable

I have removeConfig file, it contains the dir paths for removing. I need to read line by line and assign to variable. any idea? (1 Reply)
Discussion started by: redlotus72
1 Replies
Login or Register to Ask a Question
NetApp::Filer::Export(3pm)				User Contributed Perl Documentation				NetApp::Filer::Export(3pm)

NAME
NetApp::Filer::Export -- OO Class for representing NFS exports SYNOPSIS
use NetApp::Filer; my $filer = NetApp::Filer->new({ ... }); # Filer methods for querying exports: my @exports = $filer->get_exports; my @temporary_exports = $filer->get_temporary_exports; my @permanent_exports = $filer->get_permanent_exports; my @active_exports = $filer->get_active_exports; my @inactive_exports = $filer->get_inactive_exports; # Methods for accessing export attributes foreach my $export ( @exports ) { } # Methods for changing export attributes DESCRIPTION
This class encapsulates a single NFS export on a NetApp filer, and provides methods for managing them. There are related methods in the NetApp::Filer class for manging exports as a whole, but the methods in this class are specific to a single NFS export. API specific attributes This API also attempts to bring some sanity to how exports are managed, and some consistency to the interface. Most of the attributes of an export are fairly obvious, and they map directly to the options supported by "exportfs" and the /etc/exports file. This API introduces two new attributes: 'type' and 'active'; The type attribute In order to distinguish between exports which are temporary (i.e. NOT saved to /etc/exports) and those which are permanent (i.e. ARE saved to /etc/exports), this API support a "type", which be either of: permanent temporary A temporary export is one which was created using "exportfs -io", and which was not saved to /etc/exports. These exports will not survive a reboot of the filer. A permanent export is one which is found in /etc/exports. The active attribute Since you can change the export options for a filesystem temporarily (for example, by using the "fencing" option -b, or just manually specifying different options and re-exporting using -io), some permanent exports may not be in effect on the system. The active attribute is used to track these. If the active attribute is true, then the export is currently in effect. Almost by definition, all temporary exports are always active. However, if a permanent export is not in effect because a temporary export for the same pathname has been created, then such an export is considerd inactive. Global vs. Limited ro/rw Attributes The "ro" and "rw" export options really have two different modes of use. If either option is specified with no "=a[:b[:c...]]" list, then it means ALL hosts. Since this API provides methods for adding and removing entries from those lists, it treats the "all" cases special, by managing thenm as separate attributes. To specify global readonly or readwrite access, use the following options: ro_all rw_all These have boolean values. The "rw" and "ro" attributes/options are ARRAY references, each containing the list of entries for an "rw=" or "ro=" list for managing limited access. Change and Update Semantics There are several methods for changing the attributes of an export object, but in ALL cases, these merely change the object in memory. In order for the attribute change to take effect, the update method must be called, which will generate and execute the appropriate "exportfs" command. For example, suppose you wanted to remove root access for a specific hostname from all exports on a filer: my $untrusted = 'unsafe.foo.com'; my @exports = $filer->get_exports; foreach my $export ( @exports ) { if ( $export->has_root( $untrusted ) ) { $export->remove_root( $untrusted ); $export->update; } } The "remove_root" method simply removes the entry from the object in memory. The "update" method re-exports that filesystem to make the change take effect on the filer. METHODS
get_filer Returns the NetApp::Filer object for the filer on which this export exists. get_type Returns a string with one of the following values: temporary permanent indicating whether or not this particular export has been written to /etc/exports. get_active Returns a boolean value, false only if the type is "permanent", and the same export was not found in the list of currently active exports (i.e. not found in the output of "exportfs"). A temporary export is always active, by definition. get_path Returns a string representing the path for the export. Note that this may not necessarily be the same as the actual pathname of the underlying volume or qtree. get_actual Returns a string representing the "actual" path of the underlying volume or qtree for the export. If a volume or qtree as been exported using a different name, this is the actual path of the underlying object. If this export option was not used, this method will return an empty string. get_nosuid Returns a boolean value, indicating whether or not the "nosuid" option is used by the export. set_nosuid( $boolean ) This method takes a single argument, interpreted in boolean context, an sets the "nosuid" option for the export. get_anon Returns the value of the "anon" option, if set. Since this option can have the value of "0", it returns undef when this option has not been set. WARNING: be careful interpreting this in a simple boolean context. To test whether or not this option has been set use "defined". set_anon( $anon ) Takes a single argument, and sest the "anon" opton to that value. To unset this option, pass an undefined value: $export->set_anon( undef ); get_sec Returns a list of the "sec" option values. set_sec( $arrayref ) Takes a single argument, an array reference of "sec" values, which can be any of: none, sec, krb5, krb5i, or krb5p. This API does no validation of these values, so if an invalid value is given, this will result in a fatal exception when the "update" method is called. has_sec( $sec ) Takes a single string argument, and returns true if that value is found in the list of "sec" options, false otherwise. add_sec( $sec ) Takes a single string argument, and adds that value to the list of "sec" options, if not already present. remove_sec( $sec ) Takes a single string argument, and removes that value from the list of "sec" options, if present. get_root Returns a list of the "root" option values. set_root( $arrayref ) Takes a single argument, an array reference of "root" values, which can be any combination of hostnames, IP addresses, or networks. Again, no data validation is performed, so bogus values will not be detected until the export is updated on the filer, using the "update" method. To clear the root option entirely, simply pass an empty array reference. has_root( $root ) Takes a single string argument, and returns true if that value is found in the list of "root" options, false otherwise. add_root( $root ) Takes a single string argument, and adds that value to the list of "root" options, if not already present. remove_root( $root ) Takes a single string argument, and removes that value from the list of "root" options, if present. get_ro_all Returns a boolean value, indicating whether or not the "ro_all" option has been set. set_ro_all( $boolean ) Takes a single boolean argument, and sets the "ro_all" option to it's value. Setting "ro_all" to a true value will clear the "ro" list, if it exists. Also, if "ro_all" is true, then the following methods will quietly do nothing: has_ro add_ro remove_ro The "ro_all" option must be cleared (set to a false value) first. get_ro Returns a list of the "ro" entries, if any. Returns nothing if "ro_all" has been set. set_ro( $arrayref ) Takes a single argument, an array reference of "ro" values. Setting the "ro" list explicitly will set clear "ro_all" (set it to a false value). has_ro( $ro ) Takes a single argument, and returns true if that value is found in the list of "ro" options, false otherwise. If "ro_all" is true, then it always returns false. add_ro( $ro ) Takes a single string argument, and adds that value to the list of "ro" options, if not already present. If "ro_all" is true, then this method will do nothing. remove_ro( $ro ) Takes a single string argument, and removes that value from the list of "ro" options, if present. If "ro_all" is true, then this method does nothing. get_rw_all, set_rw_all, get_rw, set_rw, has_rw, add_rw, remove_rw All of these methods behave exactly the same as their "ro" counterparts described immediately above. They apply to the "rw" option, instead of "ro", but if that isn't obvious... update This method re-exports the export, using "exportfs". If ANY of the object attributes have been changed programmatically, those changes will not take effect on the filer until this method has been called. Note that updating an export will not necessarily change it's "type" from temporary to permanent, unless the "type" is explicitly changed. compare( $export ) This method takes a single NetApp::Filer::Export object, and compares the current object (that is, the one on which the method was called) to it. If they have the same basic export options, it returns true, otherwise, it returns false. Only the following options are compared: actual nosuid anon sec root rw/rw_all ro/ro_all perl v5.14.2 2008-11-26 NetApp::Filer::Export(3pm)