Special shell variables
There are some variables which are set internally by the shell and which are available to the user:

Name Description
——————————————————————————–
$1 – $9 these variables are the positional parameters.

$0 the name of the command currently being executed.

$# the number of positional arguments given to this
invocation of the shell.

$? the exit status of the last command executed is
given as a decimal string. When a command
completes successfully, it returns the exit status
of 0 (zero), otherwise it returns a non-zero exit
status.

$$ the process number of this shell – useful for
including in filenames, to make them unique.

$! the process id of the last command run in
the background.

$- the current options supplied to this invocation
of the shell.

$* a string containing all the arguments to the
shell, starting at $1.

$@ same as above, except when quoted.

Branching
if then fi
if [[ $value -eq 7 ]];then
print "$value is 7"
fi
or:

if [[ $value -eq 7 ]]
then
print "$value is 7"
fior:

if [[ $value -eq 7 ]];then print "$value is 7";fi

if then else fi
if [[ $name = "John" ]];then
print "Your welcome, ${name}."
else
print "Good bye, ${name}!"
fi

if then elif then else fi
if [[ $name = "John" ]];then
print "Your welcome, ${name}."
elif [[ $name = "Hanna" ]];then
print "Hello, ${name}, who are you?"
else
print "Good bye, ${name}!"
fi

case esac
case $var in
john|fred) print $invitation;;
martin) print $declination;;
*) print "Wrong name...";;
esac

——————————————————————————–

Looping Command Syntax for Scripts

while do done
while [[ $count -gt 0 ]];do
print "\$count is $count"
(( count -= 1 ))
done
until do done
until [[ $answer = "yes" ]];do
print -n "Please enter \"yes\": "
read answer
print ""
done
for var in list do done
for foo in $(ls);do
if [[ -d $foo ]];then
print "$foo is a directory"
else
print "$foo is not a directory"
fi
done
continue…break
One can skip the rest of a loop and directly go to the next iteration with: “continue”.

while read line
do
if [[ $line = *.gz ]];then
continue
else
print $line
fi
done
One can also prematurely leave a loop with: “break”.

while read line;do
if [[ $line = *!(.c) ]];then
break
else
print $line
fi
done

http://www.well.ox.ac.uk/~johnb/comp/unix/ksh.html

Removing accounts from predefine list:

#!/bin/ksh

done

Or course, the sleep there is just for aesthetic.. I want to see the screen

getfacl is a file utility for viewing the access control list information associated with a file or directory.

For a memory aid, you can think of ‘getfacl’ as “Get File ACL“.. ACL being Access Control List.

Access control lists are extended attributes added to most major file systems in the 2.6 kernel to improve ability to control the access of files. They allow permissions to be set for individual groups and users and not just the owning user, owning group, and all other users.

setfacl is a command that allows you to set the Access Control List information for a file or directory.

Access control lists are extended attributes added to most major file systems in the 2.6 kernel to improve ability to control the access of files. They allow permissions to be set for individual groups and users and not just the owning user, owning group, and all other users.

You can read man pages for both getfacl and setfacl for more information.

getfacl and setfacl example….

Here’s an example of using the basic funtion of getfacl and setfacl

# getfacl

#setfacl

setfacl -m default:user::rwx,default:group::r-x,default:other:r-x,default:mask:rwx /u06/OneSource/datapump_dbdump

setfacl -m default:user:rcodapp1:r-x,default:group:r-x,default:other:—,default:mas:rwx /u06/OneSouce/datapump_dbdump

I want to post… say, borrowing, the content of that page to this post for my own personal reference… Love your own page right? And since I am more likely to open SysadminPH that cuddletech, I thought we not copy the Veritas tutorial page here for my ease of access?

The Cuddletech Veritas Cheat Sheet

by: B. Rockwood
benr@cuddletech.com

Overview:
——–

The purpose of this paper is to
quickly get you up to speed in Veritas,
and to act as a quick referance. All new
users to Veritas are HIGHLY encouraged to
first read the Veritas users guides enlucded
with Veritas, and found on docs.sun.com

Remember!: Almost all commands can use several
diffrent options that are similar
across all commands. The most used
of these is “-g ” which
specifies which Disk Group the command
will be executed on. For instance,
vxinfo will only display volume information
for volumes in the rootdg, to see
volumes in the datadg, for instance, use:
Ex: “vxinfo -g datadg”

———————————————–
DISPLAY and MONITORING
———————————————–

vxdisk list
List all disks used by Veritas (VX).

vxdisk list
Display detailed information about a
single disk, including mutlipathing
information, size, type, Vx version,
and more.

vxprint
Display report style information about
the current status of all Vx componants,
including disks, subdisks, plexes, and
volumes.

vxprint
Display report style information about
the current status of ONLY the componant
you request. So for instance,
“vxprint vol01″ shows information about
all subcomponants of vol01. This works
for plexes, disk groups, etc.

vxprint -hrt
Display detailed information about all
Vx componanats, including stwdith,
ncolumns, offsets, layout type, read-
policy, and more. This is best for
a true picture of your configuration.

vxdg list
Display listing and state information
of all Disk Groups.

vxdg list
Display detailed information about
a diskgroup, including flags, version,
logs status, etc.

vxinfo
Display volume status and volume type.
By default, only displays “rootdg”,
to display a diffrent Disk Group,
use “vxinfo -g “.

vxassist maxgrow
This command will output the maximum size
the volume specified can increased by,
specified in sectors.

————————————————–
DISK TASKS and COMMANDS
————————————————–

vxdiskadd
Adds a disk to Vx by Initializing and Encapsolating
it. Specified by its device name (ex: c0t1d0s2).
NOTE: You’ll need to reboot to finalize the
disk addition!

This command, can also be used to add a disk to
a specified disk group. Just follow the prompts.
No reboots needed for changing DG’s.

vxedit rename
Rename a Vx disk. Ex: “vxedit rename disk01 disk05″

vxedit set reserve=on
Sets the “reserve” flag to a Vx disk. This
is used to keep specific disks from being
accidentally, or generally used.

vxdisk offline
Used to “offline” a disk. The disk should
be removed from its diskgroup before being
offlined.

vxdisk rm
Used to remove disks from Vx control completely.
Ex: “vxdisk rm c0t1d0s2″ Make sure to
removed the disk from its diskgroup, and offline
the disk before removing it.

vxedit set spare=on
Sets the “spare” flag to a Vx disk. This is used
to make the specified disk a hot spare, which
is then added to the “hot spare pool”.

vxedit set spare=off
Same as above but removes the disk from the
“hot spare pool”.

—————————————————-
DISK GROUPS and COMMANDS
—————————————————-

vxdg init =
Creates a new disk group, and assigns the naming
scheme to the first disk added to the group.
ex: “vxdg init newdg newdg01=c0t10d0s2″.
NOTE: This is kinda tricky because the disk that
you’re adding can’t be a member of ANY DG, but
must be initialized. It’s easier to use
“vxdiskadd”, and add the disk to a newdg by
specifying a new DG name for the DG field.

vxdg deport
Disabled a diskgroup, but doesn’t remove it. Often
used as an organized pool of disk to realocate, and
to moved DG’s from one system to another.

vxdg import
Reverse of above. Enables local access to the specified
disk group.

vxdg -n Change a Disk Groups name.

vxdg list
Use this to check the version numbers of Disk
Groups. Shows other details about the DG too.

vxdg destroy
Removes the specified DG, and frees all its disks
back to general use by Vx.

-= Quick Chart!: Disk Group Version Number Translation

VxVM Introduced Supported
Release Version Versions
——- ———— ———
1.2 10 10
1.3 15 15
2.0 20 20
2.2 30 30
2.3 40 40
2.5 50 50
3.0 60 20-60

———————————————————–
SUBDISKS and COMMANDS
———————————————————–

vxmake sd ,,
Creates a subdisk with the specified name,
and by the offset and length specified.
ex: “vxmake sd disk02-01 disk02,0,8000″
NOTE: If you are going to add this subdisk
to a plex, its good to check the other
subdisks in that plex to see what their
lengths and offsets are, use the command:
“vxprint -st”

vxedit rm
Removes a subdisk.

vxsd assoc ,….
Associates the specified subdisks to
the specified plex. Example:
“vxsd assoc vol01-03 disk01-01,disk02-01″
NOTE: Striped volumes are diffrent,
you need to specify the column# so
use the following:

vxsd -l
assoc ,…
Same as above, but used for associating
subdisks to a striped plex. Use the command
“vxprint -st” to see what other subdisk
in the plex look like, and then set the
new subdisks column number and offset
(found in the seventh column of output)
to the appropriate value.

vxsd aslog
Adds a log subdisk to the specified plex.
Ex: “vxsd aslog vol01-02 disk03-01″

vxsd dis
Disassociates the specified subdisk from its
current plex.

——————————————————
PLEXS and COMMANDS
——————————————————

vxmake plex sd=,,….
Creates a new plex by the name specified and
assigns the specified subdisks to it.

vxmake plex layout= stwidth= ncolumn= sd=…
Like above command, but specifies layout type
as defined by , which is used for creation
of striped and RAID5 plexes. The layout is
constrained by the defined number of columns,
and stripe width. Subdisks specified are
added to the created plex.

vxplex att Associates specified plex with specified volume.
(Adds a mirror)
NOTE: Attachment will take a while. Watch
it with Vxtask, or via vxprint

vxplex dis Disassociate specified plex from its connected
volume.

vxedit -r rm Remove the plex.

vxmend off Offlines a plex for repair to it’s disks.

vxplex det Detaches specified plex from its connected
volume, but maintians association with it’s
volume. The plex is no longer used
for I/O untill it is (re)attached.

vxmend fix clean Used to clean plexes that are in the
“unclean” state. Used with unstartable
volumes.

vxplex mv
Moves the data content from the origonal
plex onto a new plex.
NOTE: The old plex must be active (ENABLED).
The new plex should be the same length, or
larger than the old plex. The new plex
must not be associated with another volume.
(duh)

vxplex cp
Copies the data from the specified volume
to a new plex.
NOTE: The new plex cannot be associated
with any other volume. The new plex,
further, will NOT be attached to
the specified volume. (Also, see notes
from above)

——————————————————-
VOLUMES and COMMANDS
——————————————————-

vxassist make
Creates a new volume with the name specified
and is made to the length specified.
Ex: “vxassist make newvol 10m”
NOTE: This command will pull disk space
from the generally avalible Vx disk space.

vxassist make layout= ….
Like the above command, but with layout specified.
The most common layouts are: striped and raid5
ex: “vxassist make newvol 100m layout=raid5 disk01 disk02 disk03″
NOTE: See the vxassist(1M) man page for more information.

vxmake vol len= plex= ,…
Creates a new volume of specified length (usually
in sectors), and attachs the specified plexes to that
volume. Useful for creating volumes to house
copied or moved plexes.
NOTE: See the vxmake(1M) man page for more information.

vxvol init [plexname]
Manually sets the state of a volume.
NOTE: Not for the squimish.

vxassist maxsize [layout=raid5]
Returns the maximum size avalible via Vx to create
a new volume. By adding “layout=raid5″ to the command
the calulations take into account losse due
to raid5. Output is in sectors and Megs.

vxassist maxgrow
Returns the maximum ammount of Vx space that
can be added to the specified volume.

vxassist mirror
Creates a mirror for the specified volume.
NOTE: Think of this as “handsfree plex creation”.
This is fast, but the disks you want used
may not be used… often best to do manually.

vxassist addlog
Adds a Dirty Region Log (DRL) for the specified volume.

vxassist remove log
Reverse of above.

vxvol start
Starts a volume

vxvol stop
Stops a volume. Alternately you can use command as
such: “vxvol stopall” in order to stop all volumes.

vxassit growto/growby/shrinkto/shrinkby
Resizes the volume specified. Use one of the
following: growto, growby, shrinkto, and shrinkby
in order to descide what specifies.
By default length is specified in sectors.
This does not resize the filesystem inside the volume.
NOTE: Don’t shrink volumes to be less that
its contained filesystem! (duh)

vxvol set len=
An alternate to above command. Sets the absolute
lenths of the specified volume to the length
specified, by default, in sectors. This
does not resize the filesystem inside the volume.

NOTE: There is also a resize(1M) command, used
for resizing both volume AND filesytem. See
the man page for that one.

vxedit rm
Removes the specified volume. (poof!)
NOTE: If the volume specified is in the ENABLED
state, you will need to use the command
“vxedit -f “. Also, using the “r”
with “f” will remove all plexes and subdisks
with the volume. If you didn’t guess, “r”
is Recursive, and “f” is Force.

—————————————————————-
Misc Stuff:

To calculate the size of a filesystem inside a volume, use
the command:
fstyp -v | head -30 | grep ncg
Ignore the errors. Output will look this this:
# fstyp -v /dev/vx/rdsk/datadg/vol01 | head -30 | grep ncg
ncg 17152 size 70254592 blocks 65863396
# Broken Pipe
Unknown_fstyp (no matches)
The size found after the label “size” is presented in kilobytes.
You can convert to sectors by multiplying by 2.

———–

To calculate the size of a volume, use vxprint, and look for the
“len”. The volume length is in sectors. Convert to kilobytes
by dividing by 2.

————-

Volume Growth Procudure:
1) You can use vxassist to estimate the max size of
a given volume based on the disks you wish to add:
ex: # vxassist -g rootdg maxgrow vol01 disk01 disk02 disk03

2) Next, actually grow the volume (NOT THE FS) via the
command (assuming maxgrow outputed 10639360 as the maxsize):
ex:# vxassist -g rootdg growto vol01 10639360 disk01 disk02 disk03

3) Now VxVM grinds away, monitor with vxtask.

4) Now Grow the Filesystem, for UFS use:
# /usr/lib/fs/ufs/mkfs -F ufs -M /export /dev/vx/rdsk/rootdg/vol01 10639360

for VXFS ufs:
# /usr/lib/fs/vxfs/fsadm -b 10639360 -r /dev/vx/rdsk/rootdg/vol01 /mnt
—————————————————————

5) Done!

———-

Changing User/Group of a Raw Volume: (ex:)
vxedit -g xxxdg set group=dba data_vol_123
vxedit -g xxxdg set user=oracle data_vol_123

Thanks to Ben Rockwood! Cheers!

[root@localhost] /work/users> metastat -c d103
d103 p 32GB d100
d100 m 68GB d101 d102
d101 s 68GB c1t2d0s0
d102 s 68GB c1t3d0s0

[root@localhost] /work/users> metastat -p d103
d103 -p d100 -o 32 -b 58720256 -o 127926432 -b 8388608
d100 -m d101 d102 1
d101 1 1 c1t2d0s0
d102 1 1 c1t3d0s0

So from the first metastat -c d103.. that’s a mirrored 68G partition, d100 and a 32G soft partition d103.. We still have around 35G of space.

update: — someone comment please.. this information is incomplete!

You may set your search path automatically each time you log in, by placing the appropriate “set path” command in your “.login” file.

(To learn more about the .login file, type “help dotlogin”.) Here is a sample of a command line that you might put in your .login file to set a non-standard search path:

set path = ( $path /usr/ucb /bin /usr/bin /usr/new .)

Of course, you can use vmstat with interval, but for those sysadmin folks who are use to using Top, its still more comfortable using (and seeing) the top output.

Topas is the equivalent of Top for AIX.. it’s better than Top as a matter of fact according to some AIX gurus (and Solaris)

If you persists in using top, You’ll have to build it yourself from the sources at http://www.unixtop.org/ plus probably this fix: 

        http://sourceforge.net/tracker/index.php?func=detail&aid=934590&group_id=72892&atid=536044

Good luck!

RTFM!

Simply add NOPASSWD before the list of commands…again NOPASSWD goes before the list of commands, after your username and host list. The man page has this example:

ray rushmore = NOPASSWD: /bin/kill, /bin/ls, /usr/bin/lprm

Where ‘ray’ is the username, ‘rushmor’ is the host and the rest, you know already….

What is pwd?

pwd, when executed at the shell (prompt) will print out the current working directory in the standard output of the system, which is the monitor.

pwd could be and abbreviation for ‘print working directory’ or ‘present working directory’ or make up your own definition.. there’s no rule.

WIkipedia says:

In Unix-like and some other operating systems the pwd command (print working directory) is used to output the path of the current working directory.

The command is a shell builtin in certain Unix shells such as sh, and bash. It can be implemented easily with the POSIX C functions getcwd() and/or getwd().

The equivalent on DOS (COMMAND.COM) and Microsoft Windows (cmd.exe) is the “cd” command with no arguments. Windows PowerShell provides the equivalent “Get-Location” cmdlet with the standard aliases “gl” and “pwd”. The OpenVMS equivalent is “show default”.

Example:

$ pwd
/home/foobar

Yesterday we had to replace a failed disk that belongs to a mirror. The disk is running in a Sparc Solaris 10 box. It’s a 72GB from Fujitsu

c1t1d0           Soft Errors: 440 Hard Errors: 12 Transport Errors: 124
Vendor: FUJITSU  Product: MAY2073RCSUN72G  Revision: 0501 Serial No: 0711S0935R
Size: 73.40GB <73400057856 bytes>

As you can see from the iostat -En command, the disk is spitting hard errors and must be replaced before it can cause a lot more headache. It’s in c1t1, right.

Here’s what we’re supposed to do:

• we could delete the meta data base that corresponds to the failed disk
• detached the failed disk/slices to the mirror
• clear it
• unconfigure the disk
• replace the disk
• configure the disk
• create new meta device database
• Initialize the disk
• Attached it to mirror
• and sync

Here’s the detailed job:

Info:
metadb | grep c1t1
metadb –d c1t1d0s7

Detach:
metadetach d30 d32
metadetach d40 d42
metadetach d20 d22
metadetach d10 d12

metaclear d32
metaclear d42
metaclear d22
metaclear d12

Verify:
metastat -p | grep c1t1d0
metadb | grep c1t1d0
[root@localhost] /> cfgadm -al
Ap_Id Type Receptacle Occupant Condition
c0 scsi-bus connected configured unknown
c0::dsk/c0t0d0 CD-ROM connected configured unknown
c1 scsi-bus connected configured unknown
c1::dsk/c1t0d0 disk connected configured unknown
c1::dsk/c1t1d0 disk connected configured unknown
c1::dsk/c1t2d0 disk connected configured unknown
c1::dsk/c1t3d0 disk connected configured unknown
usb0/1 unknown empty unconfigured ok
usb0/2 unknown empty unconfigured ok
usb1/1.1 unknown empty unconfigured ok
usb1/1.2 unknown empty unconfigured ok
usb1/1.3 unknown empty unconfigured ok
usb1/1.4 unknown empty unconfigured ok
usb1/2 unknown empty unconfigured ok

Unconfigure:
cfgadm -c unconfigure c1::dsk/c1t1d0

Verify ulit, note the red text above:
cfgadm –al
SWAP DISK

Undo what has been done….

Configure:
cfgadm -c configure c1::dsk/c1t1d0

format (to label disk)

prtvtoc /dev/rdsk/c1t0d0s2 | fmthard -s – /dev/rdsk/c1t1d0s2

metadb -a –c 2 c1t1d0s7

Attach!!

metainit d32 1 1 c1t1d0s6
metainit d42 1 1 c1t1d0s4
metainit d22 1 1 c1t1d0s1
metainit d12 1 1 c1t1d0s0
metattach d30 d32
metattach d40 d42
metattach d20 d22
metattach d10 d12
metastat -p
metadevadm -u c1t1d0

And you’re done! Grab a cup of coffee and wait till the synchronization is done.

Anyhoo, today we re-jumpstarted a laboratory box because the ‘owner’ of it wants it back. Since we pretty much messed it up, I have to jumpstarted a fresh copy.

After installing returned the original /etc/shadow and /etc/passwd back from backup (had a backup file on the laptop).. but unfortunately, the /etc/shadow file is ‘null’.

Restoring File From UFSdump Backup

Here’s the procedure in restoring a particular file from ufs dump backup… Of course if you’re restoring from ufs backup you probably made a ufs backup in the first place, right? Right!

In this example, the files backup.examples and junk are restored from the pubs directory:

# cd /var/tmp
# ufsrestore if /dev/rmt/Ø
ufsrestore > ls
.:
lost+found/ pubs/

ufsrestore > cd pubs
ufsrestore > ls
./pubs:
.Xauthority .login .profile backup.examples%
.Xdefaults .mtdeletelog .wastebasket/ core
.cshrc .openwin-init Junk/ dead.letter
.desksetdefaults .openwin-init.BAK backup.examples junk

ufsrestore > add backup.examples
ufsrestore > add junk
ufsrestore > setmodes
set owner/mode for ‘.’? [yn] n
ufsrestore > extract
You have not read any volumes yet.
Unless you know which volume your file(s) are on you should start
with the last volume and work towards the first.
Specify next volume #: 1
set owner/mode for ‘.’? [yn] n
ufsrestore > quit
# ls -l
total 6
drwxrwxrwt 3 sys sys 512 Mar 11 1Ø:36 ./
drwxrwxr-x 18 root sys 512 Mar 1Ø 16:43 ../
drwxr-xr-x 2 pubs staff 512 Mar 11 1Ø:11 pubs/
# pwd
/var/tmp
# cd pubs
# ls
./ ../ backup.examples junk
#

There you go!