Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Passing options to a bash script
Top Forums Shell Programming and Scripting Passing options to a bash script Post 302197403 by nua7 on Wednesday 21st of May 2008 01:43:10 AM
Old 05-21-2008
This might also help you..Look out for $1=-g option.


Code:
# # # # # # # # # # # #
#     main section
# # # # # # # # # # # #

  print "script $(basename $0) executing $(date +%Y/%m/%d\ %H:%M:%S) \n"

#
#  only allow this script to be run by the root user
#
  if ! id | grep -q "uid=0(root)" ; then
    print "ERROR:  must be root in order to run this script"
    exit 1
  fi

  if [[ "$PLEX_ROOT" = "/claims/amxw" ]]; then
    if [[ "$NLROOTDIR" != "/claims/amxw" ]]; then
      print "ERROR: NLROOTDIR must be set to /claims/amxw in order to create a plex"
      exit 1
    fi
  fi

  if [[ "$1" = "-g" ]]; then
    shift
    print "You are obviously a plex god and have chosen to skip the approved naming convention.  Please proceed, your eminence"
    print
    mode=GOD
  else
    mode=MORTAL
  fi

  plexname=$1

  if [[ -z $plexname ]]; then
    print "ERROR: plex name isn't specified"
    exit 1
  fi

  if [[ "$mode" = "MORTAL" ]]; then
    if ! print $plexname | grep -q ^plex ; then
      print "ERROR: plex name must begin with 'plex' and be at least 9 characters"
      exit 1
    fi
  fi

 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

passing variable from bash to perl from bash script

Hi All, I need to pass a variable to perl script from bash script, where in perl i am using if condition. Here is the cmd what i am using in perl FROM_DATE="06/05/2008" TO_DATE="07/05/2008" "perl -ne ' print if ( $_ >="$FROM_DATE" && $_ <= "$TO_DATE" ) ' filename" filename has... (10 Replies)
Discussion started by: arsidh
10 Replies

2. Shell Programming and Scripting

Passing options into a script

Afternoon all, I have been writing a script to do some selects on a table dependent on what options are selected when the script is run: #!/bin/ksh set -x set -m if then echo "usage: msglog.ksh -da <date and time> -i <interface> -m <msg> -di <direction> -mi <MIR>" exit 1 fi... (3 Replies)
Discussion started by: chris01010
3 Replies

3. Shell Programming and Scripting

bash script to compile multiple .c files with some options

I'm trying to write a bash script and call it "compile" such that running it allows me to compile multiple files with the options "-help," "-backup," and "-clean". I've got the code for the options written, i just can't figure out how to read the input string and then translate that into option... (5 Replies)
Discussion started by: travis.batzer
5 Replies

4. UNIX for Advanced & Expert Users

how to add new options in bash script

what i want to be is that i would like to reinvent new options that have the same functionality as ... -u is the same functionality of conv=ucase and -l have the same functionality as conv=lcase... is there a way that i can put these in my script so that whenever i will typed in command... (12 Replies)
Discussion started by: aphryllyn1
12 Replies

5. Shell Programming and Scripting

Reading command line options from bash script

I have the following code and I am calling it using ./raytrac.bash -u and getting problems. For some reason opt_usage is still 0. opt_usage=0 iarg=0 narg=$# while (($iarg < $narg)) do (( iarg = $iarg + 1 )) arg=$argv usrInputFlag=`echo $arg | awk '/=/ {print 1}; ! /=/... (22 Replies)
Discussion started by: kristinu
22 Replies

6. Shell Programming and Scripting

Passing string from SQL to a BASH script

OS Solaris 10, DB oracle 10g Hello, We currently have a BASH script that runs and moves image files from a remote server to the local db server. A snippet of the code shows that we are picking up all Images that are 'mtime -1' some code... for file in `ssh user@10.200.200.10 'find... (3 Replies)
Discussion started by: JonP
3 Replies

7. Shell Programming and Scripting

Passing arguments to a bash script

Hi, I wanted to pass an argument to a bash script. So that the argument is used inside the awk command inside the bash script. I know the noraml way of passing argument to a bash script as below : sh myScript.sh abc Inside the bash script i can use like this myArg1=$1 wc $myArg But... (8 Replies)
Discussion started by: shree11
8 Replies

8. Shell Programming and Scripting

Passing variable from bash to perl script

Hi All, I need to pass a variable from bash script to perl script and in the perl script i am using those variables in the sql query but its giving error : Use of uninitialized value $ENV{"COUNTRYCD"} in concatenation (.) or string at /GIS_ROOT/custom/tables/DBread_vendor.pl line 50. Can ... (6 Replies)
Discussion started by: NileshJ
6 Replies

9. Web Development

Passing variable from PHP to bash script

I am totally new to PHP and I am trying to create a script that will as a user for a hostname and then use the "hostname" variable to generate a report using REST API. I am able to create the html script and php script to GET the "hostname" but I am having trouble passing the hostname variable... (10 Replies)
Discussion started by: kieranfoley
10 Replies

10. Shell Programming and Scripting

Running options in bash script

Hello UNIX & Linux Forums community! Long time Linux daily user hobbyist, new to shell scripting.... I'm working on a script that does all the "work" in one script, and makes calls to a second script to display info to the user via mostly expanding variables in heredocs. I'm contemplating... (6 Replies)
Discussion started by: Cody Learner
6 Replies

LEARN ABOUT HPUX

vxinfo

vxinfo(1M)																vxinfo(1M)

NAME

       vxinfo - print accessibility and usability of volumes

SYNOPSIS

       vxinfo [-pV] [-g diskgroup] [-o useopt] [-U usetype] [volume...]

DESCRIPTION

       The  vxinfo utility reports a usage-type-dependent condition on one or more volumes in a disk group.  A report for each volume specified by
       the volume operand is written to the standard output.  If no volume operands are given, then a volume condition report is provided for each
       volume in the selected disk group.

       Each invocation can be applied to only one disk group at a time.

OPTIONS

       -g diskgroup
		 Specify  the  disk  group for the operation, either by disk group ID or by disk group name.  If this option is not specified, the
		 default disk group is determined using the rules given in the vxdg(1M) manual page.

       -o useopt Pass in usage-type-specific options to the operation.

       -p	 Report the name and condition of each plex in each reported volume.

       -U usetype
		 Specify the usage type for the operation.  If no volume operands are specified, then the output is  restricted  to  volumes  with
		 this usage type.  If volume operands are specified, then this results in a failure message for all named volumes that do not have
		 the indicated usage type.

       -V	 Write a list of utilities that would be called from vxinfo, along with the arguments that would be passed.   The  -V  performs  a
		 preview run so the utilities are not actually called.

Volume Conditions
       The  volume  condition  is  a  usage-type-dependent  summary of the state of a volume.  This condition is derived from the volume's kernel-
       enabled state and the usage-type-dependent states of the volume's plexes.  The vxinfo utility reports the following conditions for volumes:

       Startable A vxvol startall operation would likely succeed in starting the volume.

       Started	 The volume has been started and can be used.

       Started Unusable
		 The volume has been started but is not operationally accessible.  This condition may result from errors that have occurred  since
		 the volume was started, or may be a result of administrative actions, such as vxdg -k rmdisk.

       Unstartable
		 The  volume  is  not started and either is not correctly configured or doesn't meet the prerequisites for automatic startup (with
		 volume startup) because of errors or other conditions.

OUTPUT FORMAT

       Summary reports for each volume are printed in one-line output records.	Each volume output line consists of blank-separated fields for the
       volume name, volume usage type, and volume condition.  The following example shows the volume summary:

	      bigvol	     fsgen    Startable
	      vol2	     fsgen    Startable
	      brokenvol      gen      Unstartable

       Each  plex  output  line  consists of blank-separated fields for the plex name and the plex condition.  The plex records are accompanied by
       their volume records, as the following example shows:

	      vol  bigvol	  fsgen    Startable
	      plex bigvol-01	  ACTIVE
	      vol  vol2 	  fsgen    Startable
	      plex vol2-01	  ACTIVE
	      vol  brokenvol	  gen	   Unstartable

FSGEN and GEN Usage Types
       The fsgen and gen usage types provide identical semantics for the vxinfo utility.  The fsgen and gen usage types do not support any options
       passed in with -o.  Plex conditions (reported with -p) can be one of the following:

       ACTIVE	 Either  the volume is started and the plex is enabled, or the volume was not stopped cleanly and the plex was valid when the vol-
		 ume was stopped.

       CLEAN	 The plex contains valid data and the volume was stopped cleanly.

       DCOSNP	 A data change object (DCO) plex that is attached to a volume, and which can be used by a snapshot plex to  create  a  DCO  volume
		 during a snapshot operation.

       EMPTY	 The plex is part of a volume that has not yet been initialized.

       IOFAIL	 The plex was detached because of an uncorrectable I/O failure on one of the subdisks in the plex.

       LOG	 A dirty region logging (DRL) or RAID-5 log plex.

       NODAREC	 No  physical  disk  was  found for one of the subdisks in the plex.  This implies either that the physical disk failed, making it
		 unrecognizable, or that the physical disk is no longer attached through a known access path.

       NODEVICE  A physical device could not be found corresponding to the disk ID in the disk media record for one  of  the  subdisks	associated
		 with the plex.  The plex cannot be used until this condition is fixed, or the affected subdisk is dissociated.

       OFFLINE	 The plex was disabled using the vxmend off operation.

       REMOVED	 A physical disk used by one of the subdisks in the plex was removed through administrative action with vxdg -k rmdisk.

       SNAPATT	 The  plex  is being attached as part of a backup operation by the vxassist snapstart operation.  When the attach is complete, the
		 condition changes to SNAPDONE.  A system reboot or manual starting of the volume removes the plex and all of its subdisks.

       SNAPDIS	 A vxassist snapstart operation completed the process of attaching the plex.  It is a candidate for selection by the vxplex  snap-
		 shot operation.  A system reboot or manual starting of the volume dissociates the plex.

       SNAPDONE  A  vxassist  snapstart  operation  completed  the process of attaching the plex.  It is a candidate for selection by the vxassist
		 snapshot operation.  A system reboot or manual starting of the volume removes the plex and all of its subdisks.

       SNAPTMP	 The plex is being attached as part of a backup operation by the vxplex snapstart operation.  When the	attach	is  complete,  the
		 condition changes to SNAPDIS.	A system reboot or manual starting of the volume dissociates the plex.

       STALE	 The plex does not contain valid data, either as a result of a disk replacement affecting one of the subdisks in the plex, or as a
		 result of an administrative action on the plex such as vxplex det.

       TEMP	 The plex is associated temporarily as part of a current operation, such as vxplex cp or vxplex att.  A system	reboot	or  manual
		 starting of a volume dissociates the plex.

       TEMPRM	 The plex was created for temporary use by a current operation.  A system reboot or manual starting of a volume removes the plex.

       TEMPRMSD  The  plex and its subdisks were created for temporary use by a current operation.  A system reboot or manual starting of the vol-
		 ume removes the plex and all of its subdisks.

       Volume conditions for these usage types are reported as follows:

       Startable This condition is reported if the volume is not enabled and if any of the plexes have a reported condition of ACTIVE or CLEAN.

       Started	 This condition is reported if the volume is enabled and at least one of the associated  plexes  is  enabled  in  read-write  mode
		 (which is normal for enabled plexes in the ACTIVE and EMPTY conditions).

       Started Unusable
		 This condition is reported if the volume is enabled, but the volume does not meet the criteria for being Started.

       Unstartable
		 This condition is reported if the volume is not enabled, but the volume does not meet the criteria for being Startable.

RAID-5 Usage Type
       Plexes  of RAID-5 volumes can be either data plexes (that is, RAID-5 plexes) or log plexes. RAID-5 data and log plex conditions are as fol-
       lows:

       ACTIVE	 Either the volume is started and the plex is enabled, or the volume was not stopped cleanly and the plex was valid when the  vol-
		 ume was stopped.

       CLEAN	 The  plex  contains  valid  data and the volume was stopped cleanly.  The raid5 usage type does not support any options passed in
		 with -o.

       IOFAIL	 The plex was detached from use as a result of an uncorrectable I/O failure on one of the subdisks in the plex.

       NODAREC	 No physical disk was found for one of the subdisks in the plex.  This implies either that the physical  disk  failed,	making	it
		 unrecognizable, or that the physical disk is no longer attached through a known access path.

       OFFLINE	 The plex was disabled using the vxmend off operation.

       REMOVED	 A physical disk used by one of the subdisks in the plex was removed through administrative action with vxdg -k rmdisk.

       RAID-5 data plexes can have these additional conditions:

       DEGRADED  Due to subdisk failures, the plex is in degraded mode. This indicates a loss of data redundancy in the RAID-5 volume and any fur-
		 ther failures could cause data loss.

       STALEPRTY The parity is not in sync with the data in the plex. This indicates a loss of data redundancy in the RAID-5 volume and  any  fur-
		 ther failures could cause data loss.

       UNUSABLE  This indicates that a double-failure occurred within the plex. The plex is unusable due to subdisk failures and/or stale parity.

       Log plexes of RAID-5 volumes can have the following additional conditions:

       BADLOG	 The contents of the plex are not usable as logging data.

       Volume  conditions  for	volumes of the raid5 usage type are the same as for the fsgen and gen usage types (Startable, Unstartable, Started
       and Started Unusable). In addition, the following conditions can modify the conditions:

       Degraded  This condition indicates that the RAID-5 plex of the volume is in degraded mode due to the unavailability of a  subdisk  in  that
		 plex.

       Staleprty This condition indicates that some of the parity in the RAID-5 plex is stale and requires recovery.

FILES

       /usr/lib/vxvm/type/usetype/vxinfo
				     The utility that performs vxinfo operations for a particular volume usage type.

EXIT CODES

       The  vxinfo utility exits with a non-zero status if the attempted operation fails.  A non-zero exit code is not a complete indicator of the
       problems encountered, but rather denotes the first condition that prevented further execution of the utility.

       See vxintro(1M) for a list of standard exit codes.

SEE ALSO

       vxassist(1M), vxintro(1M), vxmend(1M), vxplex(1M), vxsd(1M), vxvol(1M)

VxVM 5.0.31.1							    24 Mar 2008 							vxinfo(1M)
All times are GMT -4. The time now is 08:50 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy