Posts

Showing posts from June, 2012

Integrate Sonar with Hudson

Image
Issue:  How to Integrate SONAR with Hudson? Recently I have just come to know about SONAR. This is code reviewing tool. Currently we are using hudson as CI tool. Now we need to integrate SONAR with hudson. So that whenever someone check-in code, then it will be reviewed by SONAR before making a build.  Note : I will update later about Hudson and SONAR Installation and configuration. For the time being I am just updating about SONAR integration with hudson. If someone already configured Hudson, then it'll be helpful for them. Resolution: Actually this is having some simple steps. Hudson provide a plugin for SONAR and we need maven installed and configured with hudson for this.So below are the steps: Step 1: Download, install and start the Sonar Server.  Download the latest Sonar release from  here . Unzip the distribution to your favorite location. Based on your platform, run the batch file or the shell script from within the bin folder. Open...

Download packages using yum without Installation

How to download packages using yum without applying them? We can download packages or updates using yum downloadonly plugin without actually installing them to the system. Below steps can be followed for that. Install yum-downloadonly package. # yum install yum-downloadonly Create a directory to download packages to. # mkdir /tmp/downloadonly # Run yum in the downloadonly mode. # yum --downloadonly --downloaddir=/tmp/downloadonly packagename The above command wouldn't install package, but would just download the it to /tmp/downloadonly directory. This is the best method to download packages using yum. Command "yumdownloader" provided through "yum-utils" can also be used to download specific single packages. Thanks, Kuldeep Sharma

Prevent automatic volume group activatation at boot time

How to prevent automatic volume group activatation at boot time? Platform : Red Hat Enterprise Linux lvm Resolution In /etc/lvm/lvm.conf file add volume_list = [ "vg1" ] Which means only vg1 out of may vg's is activated at the time of booting. Other vg's will remain deactivated. Root Cause -- snip from /etc/lvm/lvm.conf -- # If volume_list is defined, each LV is only activated if there is a # match against the list. # "vgname" and "vgname/lvname" are matched exactly. # "@tag" matches any tag set in the LV or VG. # "@*" matches if any tag defined on the host is also set in the LV or VG # # volume_list = [ "vg1", "vg2/lvol1", "@tag1", "@*" ] Thanks, Kuldeep Sharma

Which access modes/flags a file was opened by an application

How to find out with which access modes/flags a file was opened by an application? Issue : We want to find out that with which access modes/flags a file was opened by as application? Platform : Red Hat Enterprise Linux(RHEL) All versions and its Supportive like Fedora, Centos etc. Resolution: The command  lsof +f g  can be used to see the access modes/flags of all open handles. The command  lsof +f g  can be used to see the access modes/flags of handles opened by a specific process id. An example output: COMMAND PID USER FD TYPE FILE-FLAG DEVICE SIZE/OFF NODE NAME [...] init 1 root 0u CHR RW,LG 1,3 0t0 3649 /dev/null init 1 root 1u CHR RW,LG 1,3 0t0 3649 /dev/null init 1 root 2u CHR RW,LG 1,3 0t0 3649 /dev/null init ...

Completely disable a RHEL user account

How to completely disable a RHEL user account? Issue We would like to know the correct way to disable all remote access to an account. Clearly, "passwd -l" (and by the same token, "usermod -L") is insufficient because that will not impact authentication by SSH public key (or other PAM modules other than pam_unix that may be enabled). Additionally, changing the shell to /bin/false or /sbin/nologin is unsatisfactory since this only affects interactive logins. Environment Red Hat Enterprise Linux (RHEL) 3, 4, 5, 6 Resolution Expiring the account via the chage utility (e.g. "chage -E 1  " will disable all access methods that use pam authentication. Root Cause Changing the shell (eg to /bin/false) is not recommended because this will only prevent interactive shell sessions for the user; since (eg) ssh port-forwarding does not require a shell (when invoked with -N option), changing the shell will not prevent users ...