another script - filtering ldapsearch result in AD

cool script from engineer ..damned , never thought life is so simple .


#!/bin/sh

LOGFILE="addadi.log"
logdir=usermod
if [ -d $logdir ]; then
echo "Using $logdir as Log directory"
else
echo "Creating $logdir as Log directory"
mkdir $logdir
fi

echo "Script Start: `date`" >> $LOGFILE

for host in ` cat hosts ` ; do
echo "Working on host: $host Time: `date`" >> $LOGFILE
fnc_check()
{
adcount=`ldapsearch cn=$host | egrep -e 'shellLNXKeyboard|shellLNXLanguage|shellLNXTimezone|shellLNXImageName|shellLNXModelName|shellLNXBuildRelease|shellLNXHardware|shellLNXBootProto|shellLNXSiteCode|shellLNXManagedBy|shellLNXComputerType'| wc -l`
echo $adcount
if [ $adcount = 10 ] || [ $adcount = 11 ]; then
echo "$host is okay" > $logdir/$host
else
echo "$host is not okay, AD attributes not complete" > $logdir/$host
fi
}

if [ $host ]; then
#/opt/adi/sbin/compadd.py -t D -s L -o rwk $host
/opt/adi/sbin/compmod.py -e ModelName=xw $host
/opt/adi/sbin/compmod.py -e Language=enUS $host
/opt/adi/sbin/compmod.py -e Keyboard=us $host
/opt/adi/sbin/compmod.py -e TimeZone=Europe/Netw $host
/opt/adi/sbin/compmod.py -e ImageName=gl-v2.2 $host
/opt/adi/sbin/compmod.py -e BuildRelease=r22 $host
/opt/adi/sbin/compmod.py -e Hardware=sda $host
/opt/adi/sbin/compmod.py -e BootProto=dhcp $host
/opt/adi/sbin/compmod.py -e ComputerType=Desktop $host
/opt/adi/sbin/compmod.py -e SiteCode=EU-rwk-rwk $host
/opt/adi/sbin/compmod.py -e ManagedBy=AH-SE $host
fnc_check
else
echo "usage: $0 hostname"
fi

done

echo "Script End: `date`" >> $LOGFILE

phrases of the day

Impossible is just a big word thrown around by small men who find it easier to live in the world they've been given than to explore the power they have to change it.

Impossible is not a fact. It's an opinion.
Impossible is not a declaration. It's a dare.

Impossible is potential.
Impossible is temporary.
Impossible is nothing.

Adopt 10 good habits that improve your UNIX® command line efficiency

Adopt 10 good habits that improve your UNIX® command line efficiency -- and break away from bad usage patterns in the process.

This article takes you step-by-step through several good, but too often neglected, techniques for command-line operations. Learn about common errors and how to overcome them, so you can learn exactly why these UNIX habits are worth picking up.

Introduction
When you use a system often, you tend to fall into set usage patterns. Sometimes, you do not start the habit of doing things in the best possible way. Sometimes, you even pick up bad practices that lead to clutter and clumsiness. One of the best ways to correct such inadequacies is to conscientiously pick up good habits that counteract them. This article suggests 10 UNIX command-line habits worth picking up -- good habits that help you break many common usage foibles and make you more productive at the command line in the process. Each habit is described in more detail following the list of good habits.
Adopt 10 good habits

Ten good habits to adopt are:

1. Make directory trees in a single swipe.
2. Change the path; do not move the archive.
3. Combine your commands with control operators.
4. Quote variables with caution.
5. Use escape sequences to manage long input.
6. Group your commands together in a list.
7. Use xargs outside of find.
8. Know when grep should do the counting -- and when it should step aside.
9. Match certain fields in output, not just lines.
10. Stop piping cats.

Make directory trees in a single swipe
Listing 1 illustrates one of the most common bad UNIX habits around: defining directory trees one at a time.

Listing 1. Example of bad habit #1: Defining directory trees individually

~ $ mkdir tmp
~ $ cd tmp
~/tmp $ mkdir a
~/tmp $ cd a
~/tmp/a $ mkdir b
~/tmp/a $ cd b
~/tmp/a/b/ $ mkdir c
~/tmp/a/b/ $ cd c
~/tmp/a/b/c $

It is so much quicker to use the -p option to mkdir and make all parent directories along with their children in a single command. But even administrators who know about this option are still caught stepping through the subdirectories as they make them on the command line. It is worth your time to conscientiously pick up the good habit:

Listing 2. Example of good habit #1: Defining directory trees with one command

~ $ mkdir -p tmp/a/b/c

You can use this option to make entire complex directory trees, which are great to use inside scripts; not just simple hierarchies. For example:

Listing 3. Another example of good habit #1: Defining complex directory trees with one command

~ $ mkdir -p project/{lib/ext,bin,src,doc/{html,info,pdf},demo/stat/a}

In the past, the only excuse to define directories individually was that your mkdir implementation did not support this option, but this is no longer true on most systems. IBM, AIX®, mkdir, GNU mkdir, and others that conform to the Single UNIX Specification now have this option.
For the few systems that still lack the capability, use the mkdirhier script (see Resources), which is a wrapper for mkdir that does the same function:

~ $ mkdirhier project/{lib/ext,bin,src,doc/{html,info,pdf},demo/stat/a}



Change the path; do not move the archive
Another bad usage pattern is moving a .tar archive file to a certain directory because it happens to be the directory you want to extract it in. You never need to do this. You can unpack any .tar archive file into any directory you like -- that is what the -C option is for. Use the -C option when unpacking an archive file to specify the directory to unpack it in:

Listing 4. Example of good habit #2: Using option -C to unpack a .tar archive file

~ $ tar xvf -C tmp/a/b/c newarc.tar.gz

Making a habit of using -C is preferable to moving the archive file to where you want to unpack it, changing to that directory, and only then extracting its contents -- especially if the archive file belongs somewhere else.


Combine your commands with control operators
You probably already know that in most shells, you can combine commands on a single command line by placing a semicolon (;) between them. The semicolon is a shell control operator, and while it is useful for stringing together multiple discrete commands on a single command line, it does not work for everything. For example, suppose you use a semicolon to combine two commands in which the proper execution of the second command depends entirely upon the successful completion of the first. If the first command does not exit as you expected, the second command still runs -- and fails. Instead, use more appropriate control operators (some are described in this article). As long as your shell supports them, they are worth getting into the habit of using them.

Run a command only if another command returns a zero exit status
Use the && control operator to combine two commands so that the second is run only if the first command returns a zero exit status. In other words, if the first command runs successfully, the second command runs. If the first command fails, the second command does not run at all. For example:

Listing 5. Example of good habit #3: Combining commands with control operators

~ $ cd tmp/a/b/c && tar xvf ~/archive.tar

In this example, the contents of the archive are extracted into the ~/tmp/a/b/c directory unless that directory does not exist. If the directory does not exist, the tar command does not run, so nothing is extracted.

Run a command only if another command returns a non-zero exit status
Similarly, the || control operator separates two commands and runs the second command only if the first command returns a non-zero exit status. In other words, if the first command is successful, the second command does not run. If the first command fails, the second command does run. This operator is often used when testing for whether a given directory exists and, if not, it creates one:

Listing 6. Another example of good habit #3: Combining commands with control operators

~ $ cd tmp/a/b/c || mkdir -p tmp/a/b/c

You can also combine the control operators described in this section. Each works on the last command run:

Listing 7. A combined example of good habit #3: Combining commands with control operators

~ $ cd tmp/a/b/c || mkdir -p tmp/a/b/c && tar xvf -C tmp/a/b/c ~/archive.tar


Quote variables with caution
Always be careful with shell expansion and variable names. It is generally a good idea to enclose variable calls in double quotation marks, unless you have a good reason not to. Similarly, if you are directly following a variable name with alphanumeric text, be sure also to enclose the variable name in square brackets ([]) to distinguish it from the surrounding text. Otherwise, the shell interprets the trailing text as part of your variable name -- and most likely returns a null value. Listing 8 provides examples of various quotation and non-quotation of variables and their effects.

Listing 8. Example of good habit #4: Quoting (and not quoting) a variable

~ $ ls tmp/
a b
~ $ VAR="tmp/*"
~ $ echo $VAR
tmp/a tmp/b
~ $ echo "$VAR"
tmp/*
~ $ echo $VARa

~ $ echo "$VARa"

~ $ echo "${VAR}a"
tmp/*a
~ $ echo ${VAR}a
tmp/a
~ $



Use escape sequences to manage long input
You have probably seen code examples in which a backslash (\) continues a long line over to the next line, and you know that most shells treat what you type over successive lines joined by a backslash as one long line. However, you might not take advantage of this function on the command line as often as you can. The backslash is especially handy if your terminal does not handle multi-line wrapping properly or when your command line is smaller than usual (such as when you have a long path on the prompt). The backslash is also useful for making sense of long input lines as you type them, as in the following example:

Listing 9. Example of good habit #5: Using a backslash for long input

~ $ cd tmp/a/b/c || \
> mkdir -p tmp/a/b/c && \
> tar xvf -C tmp/a/b/c ~/archive.tar

Alternatively, the following configuration also works:

Listing 10. Alternative example of good habit #5: Using a backslash for long input

~ $ cd tmp/a/b/c \
> || \
> mkdir -p tmp/a/b/c \
> && \
> tar xvf -C tmp/a/b/c ~/archive.tar

However you divide an input line over multiple lines, the shell always treats it as one continuous line, because it always strips out all the backslashes and extra spaces.
Note: In most shells, when you press the up arrow key, the entire multi-line entry is redrawn on a single, long input line.



Group your commands together in a list
Most shells have ways to group a set of commands together in a list so that you can pass their sum-total output down a pipeline or otherwise redirect any or all of its streams to the same place. You can generally do this by running a list of commands in a subshell or by running a list of commands in the current shell.

Run a list of commands in a subshell
Use parentheses to enclose a list of commands in a single group. Doing so runs the commands in a new subshell and allows you to redirect or otherwise collect the output of the whole, as in the following example:

Listing 11. Example of good habit #6: Running a list of commands in a subshell

~ $ ( cd tmp/a/b/c/ || mkdir -p tmp/a/b/c && \
> VAR=$PWD; cd ~; tar xvf -C $VAR archive.tar ) \
> | mailx admin -S "Archive contents"

In this example, the content of the archive is extracted in the tmp/a/b/c/ directory while the output of the grouped commands, including a list of extracted files, is mailed to the admin address.
The use of a subshell is preferable in cases when you are redefining environment variables in your list of commands and you do not want those definitions to apply to your current shell.
Run a list of commands in the current shell
Use curly braces ({}) to enclose a list of commands to run in the current shell. Make sure you include spaces between the braces and the actual commands, or the shell might not interpret the braces correctly. Also, make sure that the final command in your list ends with a semicolon, as in the following example:

Listing 12. Another example of good habit #6: Running a list of commands in the current shell

~ $ { cp ${VAR}a . && chown -R guest.guest a && \
> tar cvf newarchive.tar a; } | mailx admin -S "New archive"




Use xargs outside of find
Use the xargs tool as a filter for making good use of output culled from the find command. The general precept is that a find run provides a list of files that match some criteria. This list is passed on to xargs, which then runs some other useful command with that list of files as arguments, as in the following example:

Listing 13. Example of the classic use of the xargs tool

~ $ find some-file-criteria some-file-path | \
> xargs some-great-command-that-needs-filename-arguments

However, do not think of xargs as just a helper for find; it is one of those underutilized tools that, when you get into the habit of using it, you want to try on everything, including the following uses.
Passing a space-delimited list
In its simplest invocation, xargs is like a filter that takes as input a list (with each member on a single line). The tool puts those members on a single space-delimited line:

Listing 14. Example of output from the xargs tool

~ $ xargs
a
b
c
Control-D
a b c
~ $

You can send the output of any tool that outputs file names through xargs to get a list of arguments for some other tool that takes file names as an argument, as in the following example:

Listing 15. Example of using of the xargs tool

~/tmp $ ls -1 | xargs
December_Report.pdf README a archive.tar mkdirhier.sh
~/tmp $ ls -1 | xargs file
December_Report.pdf: PDF document, version 1.3
README: ASCII text
a: directory
archive.tar: POSIX tar archive
mkdirhier.sh: Bourne shell script text executable
~/tmp $

The xargs command is useful for more than passing file names. Use it any time you need to filter text into a single line:

Listing 16. Example of good habit #7: Using the xargs tool to filter text into a single line

~/tmp $ ls -l | xargs
-rw-r--r-- 7 joe joe 12043 Jan 27 20:36 December_Report.pdf -rw-r--r-- 1 \
root root 238 Dec 03 08:19 README drwxr-xr-x 38 joe joe 354082 Nov 02 \
16:07 a -rw-r--r-- 3 joe joe 5096 Dec 14 14:26 archive.tar -rwxr-xr-x 1 \
joe joe 3239 Sep 30 12:40 mkdirhier.sh
~/tmp $

Be cautious using xargs
Technically, a rare situation occurs in which you could get into trouble using xargs. By default, the end-of-file string is an underscore (_); if that character is sent as a single input argument, everything after it is ignored. As a precaution against this, use the -e flag, which, without arguments, turns off the end-of-file string completely.



Know when grep should do the counting -- and when it should step aside
Avoid piping a grep to wc -l in order to count the number of lines of output. The -c option to grep gives a count of lines that match the specified pattern and is generally faster than a pipe to wc, as in the following example:

Listing 17. Example of good habit #8: Counting lines with and without grep

~ $ time grep and tmp/a/longfile.txt | wc -l
2811

real 0m0.097s
user 0m0.006s
sys 0m0.032s
~ $ time grep -c and tmp/a/longfile.txt
2811

real 0m0.013s
user 0m0.006s
sys 0m0.005s
~ $

An addition to the speed factor, the -c option is also a better way to do the counting. With multiple files, grep with the -c option returns a separate count for each file, one on each line, whereas a pipe to wc gives a total count for all files combined.
However, regardless of speed considerations, this example showcases another common error to avoid. These counting methods only give counts of the number of lines containing matched patterns -- and if that is what you are looking for, that is great. But in cases where lines can have multiple instances of a particular pattern, these methods do not give you a true count of the actual number of instances matched. To count the number of instances, use wc to count, after all. First, run a grep command with the -o option, if your version supports it. This option outputs only the matched pattern, one on each line, and not the line itself. But you cannot use it in conjunction with the -c option, so use wc -l to count the lines, as in the following example:

Listing 18. Example of good habit #8: Counting pattern instances with grep

~ $ grep -o and tmp/a/longfile.txt | wc -l
3402
~ $

In this case, a call to wc is slightly faster than a second call to grep with a dummy pattern put in to match and count each line (such as grep -c).



Match certain fields in output, not just lines
A tool like awk is preferable to grep when you want to match the pattern in only a specific field in the lines of output and not just anywhere in the lines.
The following simplified example shows how to list only those files modified in December:

Listing 19. Example of bad habit #9: Using grep to find patterns in specific fields

~/tmp $ ls -l /tmp/a/b/c | grep Dec
-rw-r--r-- 7 joe joe 12043 Jan 27 20:36 December_Report.pdf
-rw-r--r-- 1 root root 238 Dec 03 08:19 README
-rw-r--r-- 3 joe joe 5096 Dec 14 14:26 archive.tar
~/tmp $

In this example, grep filters the lines, outputting all files with Dec in their modification dates as well as in their names. Therefore, a file such as December_Report.pdf is matched, even if it has not been modified since January. This probably is not what you want. To match a pattern in a particular field, it is better to use awk, where a relational operator matches the exact field, as in the following example:

Listing 20. Example of good habit #9: Using awk to find patterns in specific fields

~/tmp $ ls -l | awk '$6 == "Dec"'
-rw-r--r-- 3 joe joe 5096 Dec 14 14:26 archive.tar
-rw-r--r-- 1 root root 238 Dec 03 08:19 README
~/tmp $

See Resources for more details about how to use awk.



Stop piping cats
A basic-but-common grep usage error involves piping the output of cat to grep to search the contents of a single file. This is absolutely unnecessary and a waste of time, because tools such as grep take file names as arguments. You simply do not need to use cat in this situation at all, as in the following example:

Listing 21. Example of good and bad habit #10: Using grep with and without cat

~ $ time cat tmp/a/longfile.txt | grep and
2811

real 0m0.015s
user 0m0.003s
sys 0m0.013s
~ $ time grep and tmp/a/longfile.txt
2811

real 0m0.010s
user 0m0.006s
sys 0m0.004s
~ $

This mistake applies to many tools. Because most tools take standard input as an argument using a hyphen (-), even the argument for using cat to intersperse multiple files with stdin is often not valid. It is really only necessary to concatenate first before a pipe when you use cat with one of its several filtering options.



Conclusion: Embrace good habits
It is good to examine your command-line habits for any bad usage patterns. Bad habits slow you down and often lead to unexpected errors. This article presents 10 new habits that can help you break away from many of the most common usage errors. Picking up these good habits is a positive step toward sharpening your UNIX command-line skills.

Wifi at KLIA ...again

huhu...this time ..we at KLIA ...wifi-ing at Flyers Food Court & Cafe..above arrival hall.

Aman just arrived from Sabah , around 9pm. Before that ,Nan and I , went for dinner in food court below KLIA. Damned hungry at that time..

We started wifi around 9.15pm, Aman bought coffee for all of us ( thanks aman, you're the man ! )

luckily i brought power extension ..so that we won't having power supply problem..huhu

Fellowship of laptop owner - Starbucks Midvalley

Today in history



Me, Nan , Aman and Maku went to Starbucks Midvalley for 1 reason - surfing wireless internet together

Azwan brought his new laptop , HP Pavilion dv6100 and testdrive wifi connection , for the first time

This is my another unexpected event occured, before end of this year.

Before that , its pouring rain. Lucky Azwan arrived 10-20 minute before we reached here.

Bought some burgers ,caffe and fries, for all of us.

Need to set another date for another gathering. Today we are rushing for this event.

But still, we made it !

We all finished at 10.30pm later on ..huhu

p/s yet , need review for this event for next gathering

MacBookPro in da house ! - unexpected buy

huhu.. i never thought i would buy this machine (MacBook Pro) earlier.

After i got the money . i decided to buy the machine at MidValley Megamall. 3 things i never forgot .

1. Went to Apple shop with my Apple t-shirt
2. Buy the machine with my Apple t-shirt
3. Walk along with the machine, and i still wore the Apple t-shirt ..damned !

Freebies = Keyboard protector worth Rm89.90

Once i made a test drive on this machine, Nan and i ,went to Aman's house in Kuang and fetch him up.

but still , i need to explore more on this machine. IMHO , once i switch to Mac, i wont look behind. Never.

p/s i miss my bebe , again. Wish you were here

The Cult of Mac

today ...i bought The Cult of Mac book. This book tells all about Macintosh history and the progress of Apple computer since they evolved in this industry.
Got lots lots of pics , logos and photos in this book.

http://blog.wired.com/cultofmac/
http://wiredblogs.tripod.com/cultofmac/
http://www.nostarch.com/cult_mac.htm
http://en.wikipedia.org/wiki/Cult_of_Mac

p/s still , at Starbucks KLCC . wireless and sight-seeing..huhu . just made a phone-call for Amanyus, still in MC mood .harharharhar

wi-fi at Starbucks KLCC ...

huhu ..today i'm so bored. my girl went back to Kota Bharu , along with her beloved grandma.

i decided to go KLCC, just to have a walk around there. Huhu, i think my last visit to KLCC , last month, with my girl.

Right now, i'm surfing the Internet at Starbucks KLCC, for the first time . The connection was cool. Excellent wifi signals. Connected thru TimeZone. Lucky i still have my old account of Time Dot Com.

Before came to KLCC, i deposited my savings into HSBC account. Just in case i forgot.

huhu...need to keep my budget my expenses. still not enough to buy MacBook Pro.

p/s i miss my bebe again

phrases of the day

..so take me and let me in
Don't break me and shut me out ...

from lyric "Take Me" , Papa Roach

Netgear wireless broadband...installed!

huhu, damned!

never thought that i could surfing in my own bathroom !

after i came back seeing my girl , nazri and aman just installed the wireless router into our home, or what we called as garage.

Still , the router have its own web-based management. I'm not done yet with the testing ..but what from i heard, its the best wireless router we had.

my Fujitsu laptop still lagged ..need to reinstall the Window$ ..duhh!!

need to catch up with some knowledge with wireless Wi-Foo ...huhu

testing broadband ..at my home

11th November 2006

i have tested the internet line for the first at my my place. Overall, not bad , even my Fujitsu laptop got some lagging and intermittent, but the line still maintain.

i tested with broadband tester (http://testmy.net) and the result is between 800-900 kbps. Hehehe

However, i need to emerge my delayed-project on Gentoo.

p/s sleepy and tired...

What Not to Say at a Job Interview

1. This suit has been in my family for five generations. Fail to ace attire and grooming and you can sink your chances before you say a word.

2. You think this is disorganized. Wait till you see me on work projects. Neglecting to bring information required on the application, or bringing too few copies of your typo-free résumé, looks just plain careless.

3. I'd rather watch The Worst of C-Span than research your company. Bone up on recent new business the company has landed or write-ups about the firm in trade publications.

4. I expect you to provide the exact job I want on my terms -- now. Say too much about the job you want and you risk eliminating yourself.

5. I could care less -- but not much less. You don't want an awkward silence when asked if you have any questions. Speak up.

6. If you hire me, you'd better get your own résumé up to date. Come across as overly aggressive and you may scare the interviewer into rejecting you.

7. You might want to have security frisk me before I leave. Sharing confidential information about past or present employers will make the interviewer wonder if you can be trusted.

8. I think you're not playing with a full deck. If you're asked the "What are your weaknesses?" question, the interviewer wants a straight answer. Mention one noncritical area you'd like to polish.

9. I'm just going to go ahead and answer the question I wish you'd asked. Failing to answer the question that was actually posed will frustrate the interviewer.

10. I'll be a huge drain on company morale. A negative attitude regarding your current or past employers or colleagues will make your stock drop.

11. Ask not what I can do for you. What can you do for me? Asking questions about salary or benefits prior to getting a job offer is a major turnoff.

12. Why did we meet? Candidates who leave without underscoring their great interest in being hired are quickly forgotten.

How to determine if you are an engineer

How to determine if you are an engineer:

The only jokes you receive are through email (OUCH)

At Christmas, it goes without saying that you will be the one to find the burnt-out bulb in the string of Christmas lights.

Buying flowers for your girlfriend/boyfriend or spending the money to upgrade your RAM is a moral dilemma

If you find that you have to often explain how to use the gifts you have given other people.

Everyone else on the Alaskan Cruise is on deck peering at the scenery, and you are still on a personal tour of the engine room

In college, you thought Spring Break was metal fatigue failure

The Salespeople at Circuit City can't answer any of your questions

You are always late to meetings

You are at an air show and know how fast the skydivers are falling

You are next in line on death row in a French Prison and you find that the guillotine is not working properly, so you offer to fix it.

You bought your wife/husband a new CD ROM drive for her birthday

You forget to get a haircut (for 6 months!)

You can quote scenes from any Monty Python movie

You can type 70 words per minute but can't read your own handwriting

You can't write unless the paper has both horizontal and vertical lines

You comment to your wife/husband that her straight hair is nice and parallel

You go on the rides at Disneyland and sit backwards in the chairs to see how they do the special effects

You have Dilbert comics/paphanelia displayed anywhere in your work area

You have ever saved the power cord from a broken appliance

You have more friends on the internet than in real life

You have backed up your hard drive

You have never bought any new underwear or socks for yourself since you got married.

You have used coat hangars and duct tape for something other than hanging coats and taping ducts

You know what http:// stands for

You look forward to Christmas only to put together the kids' toys

You own one or more white short-sleeve dress shirts

You see a good design and still have to change it

You spent more on your calculator than you did on your wedding ring

You still own a slide rule and you know how to use it

You think a pocket protector is a fashion accessory

You think that when people around you yawn, it's because they didn't get enough sleep

You wear black socks with white tennis shoes (or vice versa)

You window shop at Radio Shack

You're in the backseat of your car, she/he is looking wistfully at the moon, and you're trying to locate a geosynchronous satellite

Your checkbook always balances

Your laptop computer costs more than your car

Your wife/husband hasn't the foggiest idea of what you do at work

Your wrist watch has more computing power than a 300 MHz pentium

You've already calculated how much you make per second

You've ever tried to repair a $5 radio

Your four basic food groups are: 1. Caffeine 2. Fat 3. Sugar 4.Chocolate

new script in da house..need to check first

huhu...got new script ...need to check first ...

# cat /tmp/makehome
#!/bin/ksh
#
# This script creates home directory and sets the correct permission
#

username=""
uid=""
gid=""
WCKPATH="/export/wssfs4-vol14/epw_homes"
OSSPATH="/export/nosrv02-V_S01/epw_homes"
PREFIX="/glb/home/epw_login/user_dotfiles"

read username?"Please enter username :"
read uid?"Please enter UID :"
gid=$uid

PS3="Please select user's location :"
select ch in WCK OSS
do
case $ch in
WCK )
echo "Creating home directory in $WCKPATH"
HOMEPATH=$WCKPATH
break
;;

OSS )
echo "Creating home directory in $OSSPATH"
HOMEPATH=$OSSPATH
break
esac

done

HOMEDIR=$HOMEPATH/${username}
if [ -d $HOMEDIR ]; then
echo "$HOMEDIR exists, will abort..."
exit
else
echo "Creating home directory at $HOMEDIR"
fi

mkdir ${HOMEPATH}/${username}
chmod 750 ${HOMEPATH}/${username}
chown ${uid}:${gid} ${HOMEPATH}/${username}
cp -p $PREFIX/.profile $HOMEPATH/${username}/
cp -p $PREFIX/.custom.profile $HOMEPATH/${username}/
cp -p $PREFIX/.kshrc $HOMEPATH/${username}/
cp -p $PREFIX/.custom.kshrc $HOMEPATH/${username}/
cp -p $PREFIX/.cshrc $HOMEPATH/${username}/
cp -p $PREFIX/.login $HOMEPATH/${username}/
chown ${uid}:${gid} ${HOMEPATH}/${username}/.custom.profile
chown ${uid}:${gid} ${HOMEPATH}/${username}/.custom.kshrc
chown ${uid}:${gid} ${HOMEPATH}/${username}/.cshrc
chown ${uid}:${gid} ${HOMEPATH}/${username}/.login

Prison Break ..a view from me

early this year..i'm collected full season 1 Prison Break but not have enough time to watch all of it ..

but ..after my colleagues talking about ..i'm getting addicted to this thriller tv series ..damned!

p/s , i will upload my custom-made Prison Break wallpaper (Scofield's tattoo)

wrong timing ...unplanned stayback

1:33am
23 oct 2006 , Monday

huhu ...i never thought that ERL service would stopped at 1:00 am. Damned!

But it's ok with me ...i'm used to be survivor in this kind of situation..Again ..i checked potential place to be connected to wireless signal ...i bought Nescafe Kopi Mocha , just to fill up my thirsty ( even i'm not thirsty..) ...huhu

i got great place to be connected to signals - level 3 ,centre ...near to Domestics Arrival . Connection strength = EXCELLENT! ... compared to the level 2 , centre ...the signal are intermittent = very good-> good -> low.

time by time ..i checked the connection ..still excellent ...i'm starting to love this place..

Next time , i must bring out my own extension for my AC adapter ..for me and Aman ...huhu...

all i need is to wait until 5:52 am , in order to get back to my place....in that time ..i just surfing , reading some stuffs and observe other potential place for wardriving ...wish my baby here with me ..

p/s waiting , wishing , hoping ...

A test in KLIA

11:30pm
22 Oct 2006 , Sunday

i'm testing wireless connection in KLIA area. The results - Cool!

Access point = Unknown
speed = 11 mbps
connection strength = Good

before i blogging, i'm testing the signal for the first time , at Burger King , testing for connection to digg.com and slashdot.org, but there's too much lagging, i need to move to another location to get better signals.

i also checked for plug extension for my adapter . Luckily, i got the place, level 2 , centre.

hurmm...i'm frustrated again , regarding my gentoo on LifeBook machine. Need to budget my financial with my honey. Perhaps , i could get MacBook Pro before June 2007, insya Allah

need to check other place for potential signals . Hope Aman could join me for next session of wardriving ...

...last but not least , i need to pack up my stuff , for Eid Mubarak...Miss to see my family.

p.s miss my mucuk too, love u baby

blog adjourned....

Another day in office , same cubicle

1.today , my lips not yet recovered from ulser
2.working 12 hours plus , due to Hari Raya claim.
3.need to be more cautious on my duty.
4. scripts not yet executed, need full debugging ( check with ldapsearch) ... learn..learn..learn !
5.still thinking about managing my own financial ..need my girl to be my advisor, let her decide and manage my budget.
6. my project on Gentoo still adjourned. DAMNED!
7. paid water utilities Rm7.94
8.took away Aman's slipper but he need it , my bad, bro
9.still exhausted, working 12 hours yesterday ...huk²


....
escalation
devastation
generation
separation
situation
misapatient
....


p/s however, the bottleneck is ...i need MacBook Pro badly!

scripts ...clusters...sleepy

huhu..

today i'm still searching some sample projects on clustering and MPI/LAM

some more , my team consultant wants me to create 1 or 2 scripts on searching strings in ldapsearch ... duhh!! Created new script ..just simple script

mynabo@amsdc1-n-s00006 # cat test2.ksh
#!/bin/ksh
#
# This script simplifies the adcat.py ADI script
# and includes some interactive element to the process
#

uid=""
gid=""

read gid?"Please User GID:"

echo ""
echo "Checking user account "
echo ""
echo " adcat -a passwd | grep $gid "
/opt/adi/bin/adcat.py -a passwd | grep $gid
echo ""
echo "Checking user group"
echo " adcat -a group | grep $gid "
/opt/adi/bin/adcat.py -a group | grep $gid

print " Bye Bye ! "
print " \|/ "
print " (*V*)"
print "_V___V_"
choice="no"

yesterday evening , Roxanne Hall gave presentation ( but i'm not selected for that meeting , senior only ,haha ) , on Redwood machine ( a trusted host ) ,
one of complex machine i ever saw. To be truth, i'm still learning about the cadmin thingy and archs in Redwood. Finally, it was amazing !

got to check on ksh script or shell script , need to brush up more on those stuff


p/s me ..still sleepy

A Days at my cubicle

• logging to Window$ desktop
• checking my OutLook mail
• logging to UNIX/LINUX machine ( connected to Citrix and AD LINUX ) - uptime and CPU utilization.
• updating http://del.icio.us/kevler
• reading slashdot and digg
• reading forum
• reading some stuff on HP/UX and Sun Solaris ( i got short memory )
• debugging korn Shell script ( headache!!)

p/s i miss my girl !