cd $ORIG
for x in `ls $ORIG`
do

cat $x | tr [:upper:] [:lower:] > $x.1
mv $x $PROCESSED/$x
done

## Get unique list of servers and use it to count for P1 & P3 calls

for x in `ls $ORIG`
do
for server in `cat $x | gawk ‘{FS=” - “}{print $3}’ | sort -u | grep -v ok | grep -v brownout`
do
P1_alerts=`cat $x | grep $server | grep -v brownout | grep p1 | wc -l`
P3_alerts=`cat $x | grep $server | grep -v brownout | grep p3 | wc -l`
SX_Ok_alerts=`cat $x | grep $server | grep -v brownout | grep ok | wc -l`

## Only get P1 & P3 calls per server if the calls are more than 3

if [ $P1_alerts -gt 3 ]; then  echo “$P1_alerts $server P1_alerts” >> $RESULTS/$x.res; fi
if [ $P3_alerts -gt 3 ] ; then echo “$P3_alerts $server P3_alerts” >> $RESULTS/$x.res; fi
# if [ $SX_Ok_alerts -gt 3 ] ; then echo “$server SX-OK_alerts $SX_Ok_alerts” >> $RESULTS/$x.res; fi
done
mv $ORIG/$x $PER_SERVER/$x
done

cd $RESULTS
for servers in `ls *.res`; do cat $servers | gawk ‘{print $2}` | sort -u >> servers.tmp; done

cat servers.tmp | sort -u > servers.txt
$RESULTS/per_server.sh

Example of a working while loop.

===========

!/bin/sh

counter=1

while [ $counter -le 100 ]
do

echo “This is counter = ” $counter
counter=`expr $counter + 1`

if [ $counter = 56 ]
then echo “What a lot of fun. Quiting”; exit
fi

done
==============

Following files/dirs are required for traditional Linux user management:
* /etc/passwd - contains various pieces of information for each user account

* /etc/shadow - contains the encrypted password information for user\u2019s accounts and optional the password aging information.

* /etc/group - defines the groups to which users belong

* /etc/gshadow - group shadow file (contains the encrypted password for group)

* /var/spool/mail - Generally user emails are stored here.

* /home - All Users data is stored here.

You need to backup all of the above files and directories from old server to new Linux server.
Commands to type on old Linux system

First create a tar ball of old uses (old Linux system). Create a directory:
# mkdir /root/move/
Setup UID filter limit:
# export UGIDLIMIT=500
Now copy /etc/passwd accounts to /root/move/passwd.mig using awk to filter out system account (i.e. only copy user accounts)
# awk -v LIMIT=$UGIDLIMIT -F: ‘($3>=LIMIT) && ($3!=65534)’ /etc/passwd > /root/move/passwd.mig
Copy /etc/group file:
# awk -v LIMIT=$UGIDLIMIT -F: ‘($3>=LIMIT) && ($3!=65534)’ /etc/group > /root/move/group.mig
Copy /etc/shadow file:
# awk -v LIMIT=$UGIDLIMIT -F: ‘($3>=LIMIT) && ($3!=65534) {print $1}’ /etc/passwd | tee - |egrep -f - /etc/shadow > /root/move/shadow.mig
Copy /etc/gshadow (rarely used):
# cp /etc/gshadow /root/move/gshadow.mig
Make a backup of /home and /var/spool/mail dirs:
# tar -zcvpf /root/move/home.tar.gz /home
# tar -zcvpf /root/move/mail.tar.gz /var/spool/mail

Where,

* Users that are added to the Linux system always start with UID and GID values of as specified by Linux distribution or set by admin. Limits according to different Linux distro:
o RHEL/CentOS/Fedora Core : Default is 500 and upper limit is 65534 (/etc/libuser.conf).
o Debian and Ubuntu Linux : Default is 1000 and upper limit is 29999 (/etc/adduser.conf).
* You should never ever create any new system user accounts on the newly installed Cent OS Linux. So above awk command filter out UID according to Linux distro.
* export UGIDLIMIT=500 - setup UID start limit for normal user account. Set this value as per your Linux distro.
* awk -v LIMIT=$UGIDLIMIT -F: \u2018($3>=LIMIT) && ($3!=65534)\u2019 /etc/passwd > /root/move/passwd.mig - You need to pass UGIDLIMIT variable to awk using -v option (it assigns value of shell variable UGIDLIMIT to awk program variable LIMIT). Option -F: sets the field separator to : . Finally awk read each line from /etc/passwd, filter out system accounts and generates new file /root/move/passwd.mig. Same logic is applies to rest of awk command.
* tar -zcvpf /root/move/home.tar.gz /home - Make a backup of users /home dir
* tar -zcvpf /root/move/mail.tar.gz /var/spool/mail - Make a backup of users mail dir

Use scp or usb pen or tape to copy /root/move to a new Linux system.
# scp -r /root/move/* user@new.linuxserver.com:/path/to/location
Commands to type on new Linux system

First, make a backup of current users and passwords:
# mkdir /root/newsusers.bak
# cp /etc/passwd /etc/shadow /etc/group /etc/gshadow /root/newsusers.bak

Now restore passwd and other files in /etc/
# cd /path/to/location
# cat passwd.mig >> /etc/passwd
# cat group.mig >> /etc/group
# cat shadow.mig >> /etc/shadow
# /bin/cp gshadow.mig /etc/gshadow

Please note that you must use >> (append) and not > (create) shell redirection.

Now copy and extract home.tar.gz to new server /home
# cd /
# tar -zxvf /path/to/location/home.tar.gz

Now copy and extract mail.tar.gz (Mails) to new server /var/spool/mail
# cd /
# tar -zxvf /path/to/location/mail.tar.gz

Now reboot system; when the Linux comes back, your user accounts will work as they did before on old system:
# reboot

Please note that if you are new to Linux perform above commands in a sandbox environment. Above technique can be used to UNIX to UNIX OR UNIX to Linux account migration. You need to make couple of changes but overall the concept remains the sam

First of all install the following fileset:bos.cifs_fs

Once you have the fileset installed and CIFS running, use this command to create the mount point.

# smitty communications

And mount the CIFS / SMB fileshare from there.

Only problem with this way is that if the share requires Windows domain credentials, you get stuck, as you need to add “wrkgrp=domain name”

You can use the command line syntax shown below to do that

mount -v cifs -n servername/username/password-owrkgrp=domainname,fmode=755 sharename /mount point

To have the mount point survive a server reboot, add it to /etc/rc.nfs like this.
/usr/sbin/mount -v cifs -n servername/username/password -o wrkgrp=domain name,fmode=755 sharename /mount point

Just this other day - I got a situation in which I needed to backup an LPAR (logical partition) on an IBM p520 server with IVM (Integrated Virtualization Management) installed.

Unlike in a VIOS (Virtual Input/Output Server) LPAR environment, you can not allocate (for now at least) a tape drive to an LPAR on the IVM.

A remote, secure, backup solution, through the IVM LPAR, that does not use NFS had to be devised, and this is how:

Scenario:

p520 with 2 LPARS: IVM & Snowwhite (client LPAR)

- Tape on IVM.

- IVM LPAR running IOS 1.3.0

- Snowwhite LPAR running AIX 5.3

1. Install ssh on Snowwhite

Get the AIX Toolbox for Linux, and ftp the following packages to snowwhite in /tmp.

openssh.base, openssh.license & openssh.man.en_US

Get the AIX 5.3 Expansion Pack CD and ftp the openssl-0.9.7g-1.aix5.1.ppc.rpm file to /tmp on Snowwhite.

Telnet onto Snowwhite and run:

rpm -ihv openssl-0.9.7g-1.aix5.1.ppc.rpm

smitty installp

Remember to install packages in /tmp.

2. Setup a backup account on the IVM LPAR

Use the web-browser to create a user on the IVM LPAR, let’s call that user, bkpuser

Telnet /ssh onto the IVM LPAR and change the shell for bkpuser from rksh to ksh.

3: Generate an ssh rsa public key so that you do not have to use a password everytime you want to access IVM via SSH for backup purposes.

On Snowwhite, as root,

# key-gen -t rsa

The rsa public key will be generated.

Ftp/Copy this key to /home/bkpuser/.ssh/authorized_keys2 file on the IVM server.

4: Now the backup part

Test the remote backup using:

# tar -cpvf - /usr | ssh -l bkpuser ivm “/usr/bin/dd of=/dev/rmt0 obs=20b”

5: Now the restore part

Suppose one of the files inside the backup is /tmp/openssh.base, restore as follows:

#ssh -l bkpuser ivm “dd if=/dev/rmt0 obs=20b” | tar -xpvf - /tmp/openssh.base

Cheers

—————————————

Found the Zoundry software to be easier to use interms of uploading documents other than pictures.

I like uploading word and pdf documents to my blog. Blogdesk would not do it with ease.

Zoundry met all my expectations.

Folks there, if there is anyone with a better client, please just comment and paste the link to it on this blog.

Cheers

Gary

Powered by Zoundry

We had a good time of worship and fellowship. So sweet and good that we left Hamilton after 7pm.

Had the misfortune of getting a vehicle breakdown just after getting back to Auckland, in Takanini. Sister Rachel helped us to get the vehicle towed home (God bless her!).

Apart from this mishap, we had a jolly good time.

Looking forward to more.

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

A couple of songs:

Gospel Choruses

Gospel songs

We had a good time of fellowship. People got to know each other more. New friendships were forged.
The food was just fantastic.

There was a resounding call for another such to be held in the not too distant future. And I think I am in agreement with this motion.

Thanks to Bro. George for assisting with the arrangements through his membership in the club.

Brother Charles closed with a word of prayer.

Thanks to all the men that attended. Your support is appreciated.
Psalms, chapter 133
1 : Behold, how good and how pleasant it is for brethren to dwell together in unity!
2 : It is like the precious ointment upon the head, that ran down upon the beard, even Aaron’s beard: that went down to the skirts of his garments;
3 : As the dew of Hermon, and as the dew that descended upon the mountains of Zion: for there the LORD commanded the blessing, even life for evermore.

Fellow men in IRC, it’s your participation which make the difference!

Let’s continue to make a difference.
Regards

Gary

Mirroring Logical Volumes & Striping: aix_lv_mirror_and_striping.txt

Next Men’s Meeting will be at Bro Ojisi’s place on Friday 15 September 2006 at 7.30pm in Dannemora.

e.t