Nibble of Thoughts

I have a RHEL5 DVD but it is difficult to install a package using rpm because I need to manually add all dependent packages. Here is now I create a Yum reposiroty so that I can use yum to install these packages. Note that the DVD is automatically mounted as /media/RHEL_5.1 x86_64 DVD.

> cd /media/RHEL5_5.1\ x86_64\ DVD/Client
> rpm -ihv createrepo-0.4.4-2.fc6.noarch.rpm
> cd /home/blah/some_dir
> createrepo -vpo /home/blah/some_dir /media/RHEL5_5.1\ x86_64\ DVD
> cd /home/blah/some_dir
> ln -s /media/RHEL5_5.1\ x86_64\ DVD/Client Client
> ln -s /media/RHEL5_5.1\ x86_64\ DVD/Workstation Workstation

Then create a file /etc/yum.repos.d/DVD.repo with the following content

[dvd]
name=RHEL4 DVD
baseurl=file:///home/blah/some_dir
enabled=1
gpgcheck=0

Run
> yum update

and you are done.

Yesterday I needed to access a web-based application requiring JRE Plugin.
Guess what the web-page told me, there is no Java plugin installed.
The very first thing I did was to type about:plugins in the address-bar.
Sure enough there was no mention of the java plugin. Then I checked to see if JRE was installed - which was, by the way.
The very next thing was to see if there was link for the plugin in the ~/.mozilla/plugins directory.
There was no libjavaplugin_oji.so. So creating the link finally solved the issue for me.

In short, if you don't see Java plugin, do the following:
ln -s /usr/lib/jvm/java-6-sun-1.6.0.13/jre/plugin/i386/ns7/libjavaplugin_oji.so /home/murlee/.mozilla/plugins/

Recently my laptop speaker conked off, and I have been using the earplugs since then.
But there is this irritating high-pitched beep which occurs every time there is a keyboard error, and it can really hurt.

I tried unsetting Beep from the gnome-sound-properties, but to no avail.
Finally I found a way to do this, and I am sure my ears are much happier now.

$ /usr/openwin/bin/xset b 0
$ /usr/openwin/bin/xset b off
$ /usr/openwin/bin/xset -b

1. Determine the interface to setup the DHCP for.
* You can either plumb all and see : $ ifconfig -a plumb
* Or you can get it using : $ dmesg | grep ether

2. Create empty file /etc/hostname.interface : $ touch /etc/hostname.bfe0

3. Create empty file /etc/dhcp.interface : $ touch /etc/dhcp.bfe0
This file may contain the following directives:
* wait time=time in secs
* primary

NOTE: DHCP client daemon, dhcpagent will be started only if /etc/dhcp.interface file exists.

Reference:

1. Setting up a Solaris DHCP client by Rich Teer
2. Configuring network interface cards by Lance Spitznet
3. Solaris DHCP client at Sun Solaris documentation web site

Fenxi is a pluggable Java-based post-processing performance analysis tool. For a brief overview on Fenxi, please read Neel's blog.

So what is all this talk about Fenxi, where do I get it and how do I use it?

Fenxi is a post-processing tool and does not collect the metrics. It has built-in parsers for handling the output from tools such as mpstat, iostat, vmstat, etc. (Refer to user-manual for complete list.) and publishes the processed results in HTML format.

Fenxi has been published on Java.Net and is available as a binary or via CVS from http://fenxi.dev.java.net.

Download the latest fenxi binary package and untar the package as follows:
gzcat fenxi-latest.tar.gz | tar xvf -
Make sure that you have Java 1.5 or above and Perl 5.6 or greater installed.

To run a simple test on Fenxi, here's what you do.

1. Create a directory, say Fenxi_Test.
2. Generate mpstat and vmstat outputs and store them as mpstat.out, vmstat.out respectively:
   mpstat 1 10 > Fenxi_Test/mpstat.out
vmstat 1 10 > Fenxi_Test/vmstat.out
3. Now that you have your performance data, we can go ahead and process them. To process it with Fenxi, run:
   fenxi process Fenxi_Test Fenxi_Test/html Run1
4. This generates and output like:

       Creating database ...                            4.34s
       Parsing raw files ...                            2.25s
       Loading create statements from txt
       Loading vmstat_out                               ...+..+..+..OK
       Loading mpstat_out                               ...+..+..+..OK
       Processing profile default_profile               ...OK
       | Generating section   39/39       0 errors
       Query Execute took                               5.86s
       HTML Generation took                             2.03s
   

5. The processed HTML files are new available in Fenxi_Test/html directory and can be viewed in a browser. If there are any errors in the format of the file, it would show the number of errors, and we can drill down using fenxi.log. For any database errors, we can look into derby.log for further details.

Fenxi can also be used to compare two or more runs.

1. Create directory Fenxi_Test2 and redo the steps in simple test, replacing Fenxi_Test with Fenxi_Test2. This will generate the mpstat.out and vmstat.out files and have them processed using:
   fenxi process Fenxi_Test2 Fenxi_Test2/html Run2
2. Compare the two runs using:
   fenxi compare Fenxi_Test/html Fenxi_Test2/html Fenxi_compare
3. The output can be viewed on a browser via the index.html file created in the Fenxi_compare directory.

Expect future blogs on the various features of Fenxi and how to customize it.