NET USE command

The NET USE command is used to associate a local drive letter or device name with a shared network drive or device. Most often, the NET USE command is used for network drive mapping.

The NET USE command can be used also to disconnect a computer from a shared resource, or to display information about computer network connections.

1.How do I display a list of network connections on my computer

Go to yoStart menu--> Run, type cmd and hit enter. Then, type NET USE and you will see

a list of connected network devices

2.How do I disconnect from a share using NET USE?

NET USE [driveletter: or share] /DELETE

Eg : net use z: /delete

net use \\share1\softwares /delete

In some case you want to map the share with another user credentials, and in such situations use the netuse / delete command as explained above to terminate the sessions properly

Managing Terminal Services Sessions Remotely

Normally windows has a limitation of maximum 2 user session in terminal service administration mode

Many times you might have faced problem in connecting to Terminal Services because both sessions are used up. I can use another server to check the status of the first one. As long as the logged in user has administrative rights on the non-accessible machine I would run this:

qwinsta /server:10.196.10.2

Where, 10.196.10.2 is the IP address or name of the non-accessible machine.

This will display something like this:

qwinsta /server:10.196.10.2

SESSIONNAME USERNAME ID STATE TYPE DEVICE

console 0 conn wdconn

rdp-tcp 65536 Listen rdpwd

rdp-tcp#470 Steve 1 Active rdpwd

rdp-tcp#471 Rajesh 3 Active rdpwd

Now I know that Steve and Rajesh are the two that are logged in. Since I know that Rajesh has left the office sometimes ago and might have forgotten to log off, I have decided to terminate his session.

To disconnect Rajesh's session I would type this:

rwinsta /server:10.196.10.2 3

Notice the 3 which is the session ID I found from using qwinsta above.

There is another command, “query “which can serve the same purpose , but i prefer using qwinsta (Query Windows Station) and rwinsta (Reset Windows Station) as they are fully compatible with W2K ,WinXP , W2K3 and win2k8

Installing and Upgrading Perl module using PPM

This post describes how to install/upgrade perl modules using PPM on windows

1. To install a new package run ppm command from the command prompt

ppm install

eq: C:\PERL>ppm install Text::CSV_XS

2. To upgrade an existing package use the ppm upgrade command

ppm upgrade --install


In the following example we are trying to upgrade the Text::CSV_XS module

2.1 Check the current version

C:\PERL>perl -MText::CSV_XS -e "print $Text::CSV_XS::VERSION"
0.23

2.2 Update the current version

C:\PERL>ppm upgrade --install Text-CSV_XS
Text-CSV_XS 0.23: new version 0.65 available in Autonamed 3
Text-CSV_XS 0.23: new version 0.65 available in Autonamed 2
Text-CSV_XS 0.23: new version 0.35 available in ActiveState Package Repository
Text-CSV_XS 0.23: new version 0.35 available in ActiveState PPM2 Repository

Note: Text-CSV_XS version 0.23 is available from more than one place.
Which repository would you like to upgrade from?

1. Autonamed 3
2. Autonamed 2
3. ActiveState Package Repository
4. ActiveState PPM2 Repository

Repository? [ActiveState PPM2 Repository] 1
====================
Upgrade 'http://ppm.tcool.org/archives/Text-CSV_XS.ppd' version 0.65 in ActivePerl 5.8.2.808.
====================
Files found in blib\arch: installing files in blib\lib into architecture dependent library tree
Installing C:\Perl\site\lib\auto\Text\CSV_XS\CSV_XS.dll
Installing C:\Perl\site\lib\auto\Text\CSV_XS\CSV_XS.exp
Installing C:\Perl\site\lib\auto\Text\CSV_XS\CSV_XS.lib
Installing C:\Perl\site\lib\auto\Text\CSV_XS\CSV_XS.pdb
Installing C:\Perl\site\lib\Text\CSV_XS.pm
Writing C:\Perl\site\lib\auto\Text\CSV_XS\.packlist
Successfully upgraded Text-CSV_XS version 0.65 in ActivePerl 5.8.2.808.

2.3 Check the version again

C:\PERL>perl -MText::CSV_XS -e "print $Text::CSV_XS::VERSION"
0.65

Modifying Swap file size

Sometimes it is necessary to add more swap space after installation. For example, you may upgrade the amount of RAM in your system from 1024 MB to 2048 MB, but there is only 2048 MB of swap space. It might be advantageous to increase the amount of swap space to 3072 MB if you perform memory-intense operations or run applications that require a large amount of memory.

You have two options: add a swap partition or add a swap file. It is recommended that you add a swap partition, but that can be difficult if you do not have any free space available.

The example below assumes you don’t have an additional free space available to create a partition so we will be adding a swap file to enable more swap space

To add a swap file:

Determine the size of the new swap file in megabytes and multiple by 1024 to determine the block size. For example, the block size of a 64 MB swap file is 65536.

Here we want to add additional 1024 MB to increase the swap space to 3072 from 2048

1.At a shell prompt as root, type the following command with count being equal to the desired block size:

dd if=/dev/zero of=/swapfile bs=1048576 count=1024

2.Setup the swap file with the command:

mkswap /swapfile

3.To enable the swap file immediately but not automatically at boot time:

swapon /swapfile

4.To enable it at boot time, edit /etc/fstab to include:

Echo “/swapfile swap swap defaults 0 0” >> /etc/fstab

The next time the system boots, it enables the new swap file.

5.After adding the new swap file and enabling it, you can verify it is enabled by the following commands

# cat /proc/swaps

# free –m

To Remove a swap file

1.At a shell prompt as root, execute the following command to disable the swap file (where /swapfile is the swap file):

swapoff /swapfile

2.Remove its entry from /etc/fstab

3.Remove the actual file:

rm /swapfile

If you want to disable an additionally added swap partition use the swapoff on that partition and then remove the fstab entries

for eq:

swapoff /dev/hdb3

Installing Bugzilla

Bugzilla is a bug-tracking system from mozilla.org. Bugzilla is enterprise-class piece of software that tracks bugs and issues for hundreds of organizations around the world.

Step 1: Create server say bugzilla.mydomain.com

Setup hostname, network, dns etc properly

Step 2 : Install the following prerequisites

Before installing see bugzilla documentation for supported versions for the package you are going to install

•Install MTA
#yum install sendmail*
•Install database server
#yum install mysql-server
•Install web server
#yum install httpd-*
•Install Perl
#Yum Install perl-*
#yum install ImageMagick-devel

Step 3 : Configure sendmail to send and recive email

You may need to configure your DNS server properly to set your email server to send and receive email. By default send mail will listen port on 25 in 127.0.0.1 only ,Change DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl as below

#vi /etc/mail/sendmail.mc

dnl #DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl

#m4 /etc/mail/sendmail.mc > /etc/mail/sendmail.cf
#service sendmail restart
#chkconfig sendmail on

Note: - [Please see send mail documentation for any additional configurations]

Step 4 : Setup Database Server

•Start mysql server
#service mysqld start
•Set mysqladmin password
# mysqladmin password ********

Step 4.1: Allow large attachments and many comments

By default, MySQL will only allow you to insert things into the database that are smaller than 64KB. To change MySQL’s default, you need to edit your MySQL configuration file, which is usually /etc/my.cnf on Linux.

# vi /etc/my.cnf

[mysqld]
max_allowed_packet=10M

Step 4.2: Allow small words in full-text indexes

By default, words must be at least four characters in length in order to be indexed by MySQL’s full-text indexes. This causes a lot of Bugzilla specific words to be missed, including "cc", "ftp" and "uri".
MySQL can be configured to index those words by setting the ft_min_word_len param to the minimum size of the words to index. This can be done by modifying the /etc/my.cnf according to the example below:

# vi /etc/my.cnf
[mysqld]
# Allow small words in full-text indexes
ft_min_word_len=2

Step 4.3: create a database user to use for bugzilla

You need to add a new MySQL user for Bugzilla to use. (It’s not safe to have Bugzilla use the MySQL root account.) You will need the $db_pass password later to set in localconfig . I used SQL GRANT command to create a “bugs” user. This also restricts the “bugs”user to operations within database called “bugs”, and only allows the account to connect from “localhost”. Modify your setup if you will be connecting from another machine or as a different user. Replace $db_password with your proffered password


mysql> GRANT SELECT, INSERT,UPDATE, DELETE, INDEX, ALTER, CREATE, LOCK TABLES,CREATE TEMPORARY TABLES, DROP, REFERENCES ON bugs.* TO bugs@localhost IDENTIFIED BY ’$db_password’;

mysql> FLUSH PRIVILEGES;

Step 4.4 . Permit attachments table to grow beyond 4GB Note: [This has to be done only after completing bugzilla installation]

By default, MySQL will limit the size of a table to 4GB. This limit is present even if the underlying filesystem has no such limit. To set a higher limit, follow these instructions. After you have completed the rest of the installation (or at least the database setup parts), you should run the MySQL command-line client and enter the following, replacing $bugs_db with your Bugzilla database name (bugs by default):

mysql> use $bugs_db
mysql> ALTER TABLE attachments AVG_ROW_LENGTH=1000000,MAX_ROWS=20000;

Step 5: Setup webserver

Normally you will have to add set the server name and specify the document root directory .
Note [ Follow apache/httpd documentation for any advance configurations]

#vi /etc/httpd/conf/httpd.conf

ServerName bugzilla.mydomain.com


#service httpd restart
#chkconfig httpd on

Setup 6: Install Bugzilla

Download the latest package from bugzilla and unzip it

#tar -xvzf bugzilla-3.4.1.tar.gz
#mv bugzilla-3.4.1 /var/www/html/
# chown -R 751 bugzilla-3.4.1/
#chown root:apache -R bugzilla-3.4.1/


Step 7: Edit localconfig

#vi /var/www/html/bugzilla/localconfig

Set database password , username , location of dot /usr/bin/dot etc here

Step 10: Install all required modules

#cd /var/www/html/bugzilla/

Check whether all required modules are installed or not using checksetup.pl --check-modules
#./checksetup.pl --check-modules

Install any missing modules
eg: #/usr/bin/perl install-module.pl GD::Text

Step 11: Run checksetup.pl

After resolving all dependencies you can install bugzilla by running the below command

#./checksetup.pl


Step 12: Verify whether bugzilla is accessible

At this point we will be able to upgraded bugzilla instance bu accessing http://bugzilla.mydomain.com/bugzilla


Well .... its ready do some customization and play with bugs:-)

How to find include path (@INC) for installed Perl environment?

Methode 1: You can run the following commands to get the @INC path

perl -e "print qq(@INC)"

You can just run that command from the both Linux and dos command line.

The output from this command on Windows PC will looks like this:

C:/Perl/lib C:/Perl/site/lib .

The output from Linux server will looks like this:

/usr/lib/perl5 //usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl .

Methode 2: Alternatively you can use #perl -V to find out included paths along with other information's

Use perl -V to see the include paths @INC

The output from Linux server will looks like this:

/usr/lib/perl5/5.8.0/i386-linux-thread-multi

/usr/lib/perl5/5.8.0

/usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi

/usr/lib/perl5/site_perl/5.8.0

/usr/lib/perl5/site_perl

/usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi

/usr/lib/perl5/vendor_perl/5.8.0

/usr/lib/perl5/vendor_perl

Installing Jboss On Linux

This blog decribes how to install and setup jboss to start automatically on RedHat Linux

Step1: Install Java and set environment variables

Please follow this link for instructions

http://easylinuxstuffs.blogspot.com/2009/08/installing-java-on-linux.html

Step2: Create a user called jboss

It always advisable to create a user "jboss" that can be used to start/stop jboss and can be assign permissions

#useradd jboss

Step3: Download appropriate package from Jboss and Install it

#tar -xvxf jboss-5.1.0.GA-jdk6.zip

#mv jboss-5.1.0.GA /usr/local/

#chown -R jboss:jboss /usr/local/jboss-5.1.0.GA

Step4: Set Environment variables for JBOSS

Create a file /etc/profile.d/jboss

# touch /etc/profile.d/jboss

# chmod +x /etc/profile.d/jboss

#vi /etc/profile.d/jboss ( Add the following entries)

#***** Set Env Variables for Jboss

JBOSS_HOME=/usr/local/jboss-5.1.0.GA

export JBOSS_HOME

export PATH=$JBOSS_HOME/bin:$PATH

export LAUNCH_JBOSS_IN_BACKGROUND=1

Step5: Logout from shell to get the above path settings updated

Note: [Instead of creating /etc/profile.d/jboss we can always update the variables in /etc/profile]

Step6: Configure Jboss to script start automatically on restart

Starting from JBoss 4.0.1 and above a sample start-up script ( eq: jboss_init_redhat.sh for redhat) is supplied with the package , we just need to modify it

Copy the script to /etc/init.d and name it as jboss

#cp /usr/local/jboss-5.1.0.GA/bin/jboss_init_redhat.sh /etc/init.d/jboss

#chmod +x /etc/init.d/jboss

Step7: create links

The links will be used to identify at which run levels JBoss should be started and stopped.

#ln -s /etc/rc.d/init.d/jboss /etc/rc3.d/S84jboss

#ln -s /etc/rc.d/init.d/jboss /etc/rc5.d/S84jboss

#ln -s /etc/rc.d/init.d/jboss /etc/rc4.d/S84jboss

#ln -s /etc/rc.d/init.d/jboss /etc/rc6.d/K15jboss

#ln -s /etc/rc.d/init.d/jboss /etc/rc0.d/K15jboss

#ln -s /etc/rc.d/init.d/jboss /etc/rc1.d/K15jboss

#ln -s /etc/rc.d/init.d/jboss /etc/rc2.d/K15jboss

Linux will execute the equivalent of "service jboss start" for the "S" links and "service jboss stop" for the K links.

Red Hat has a chkconfig command to manage these links, which may or may not work (it uses comments in the top of the script to determine which run-levels it should be started/stopped in)

Step8: Modify the script to work with chkconfig command in Redhat

Add the following entries just after #!/bin/sh in the script

#

# JBoss Control Script

#

# chkconfig: 345 80 20

# description: JBoss Startup File

#

#

# To use this script run it as root - it will switch to the specified user

#

Step9: Modify the script with JJboss,JavaPath, User and Host details

Find out the following entries and change according to you installation directories and path

#define where jboss is - this is the directory containing directories log, bin, conf etc

JBOSS_HOME=${JBOSS_HOME:-"/usr/local/jboss-5.1.0.GA"}

#define the user under which jboss will run, or use 'RUNASIS' to run as the current user

JBOSS_USER=${JBOSS_USER:-"jboss"}

#make sure java is in your path

JAVAPTH=${JAVAPTH:-"/usr/java/jdk1.6.0_14/bin"}

#bind jboss services to a specific IP address - added by rasith

JBOSS_HOST=${JBOSS_HOST:-"yourserver.yourdomain.com"} Note:[Either give FQDN of your server or IP Address]

Step10: set chkconfig to start jboss in different runlevel

#chkconfig --level 345 jboss on

Step11: Start Jboss and Verify whether it is running properly

#/sbin/service jboss start

You should be able to see jboss up and running at http:://yourserver.yourdomain.com:8080

Use /sbin/service jboss start|stop|restart to start , stop and to restart jboss

Stept12: Restart your server and verify jboss is running automatically after the restart