<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:blogger='http://schemas.google.com/blogger/2008' xmlns:georss='http://www.georss.org/georss' xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-1019359938654970995</id><updated>2024-12-18T21:42:12.865-08:00</updated><category term="Linux"/><category term="System Admin"/><category term="Installation"/><category term="LinuxNewbie"/><category term="Troubleshooting"/><category term="Kernel"/><category term="Xorg"/><category term="389-ds"/><category term="Apache"/><category term="Cron"/><category term="Fedora DS"/><category term="GCC"/><category term="GRUB"/><category term="Git"/><category term="Jboss"/><category term="LVM"/><category term="New Releases"/><category term="Nginx"/><category term="PAE"/><category term="RHEL5"/><category term="RPM"/><category term="SSH"/><category term="Samba"/><category term="Solaris"/><category term="Swap"/><category term="Unix"/><category term="Version Control System"/><category term="Virtualbox"/><category term="Virtualization"/><category term="Web Server"/><title type='text'>..A Place for Linux Enthusiasts</title><subtitle type='html'>..A Place for Linux Enthusiasts</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://linuxscoop.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default?redirect=false'/><link rel='alternate' type='text/html' href='http://linuxscoop.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><link rel='next' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default?start-index=26&amp;max-results=25&amp;redirect=false'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>57</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><blogger:adultContent>true</blogger:adultContent><entry><id>tag:blogger.com,1999:blog-1019359938654970995.post-1289062429044450039</id><published>2011-08-12T19:59:00.000-07:00</published><updated>2011-08-12T20:15:06.425-07:00</updated><title type='text'>Setting up automatic startup script for Solaris 10 Update 9</title><content type='html'>To have your applications automatically start at boot time on Solaris, there are 2 ways: SMF and Legacy Init Scripts.&lt;br /&gt;&lt;br /&gt;Legacy Init Scripts are old fashioned, used forever on System V based UNIX. They typically look something like this:&lt;br /&gt;&lt;br /&gt;Code:&lt;br /&gt;&lt;br /&gt;$ cat /etc/init.d/acct&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;    &lt;br /&gt;&lt;br /&gt;#!/sbin/sh&lt;br /&gt;state=&quot;$1&quot;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;    &lt;br /&gt;&lt;br /&gt;case &quot;$state&quot; in&lt;br /&gt;&#39;start&#39;)&lt;br /&gt;&lt;br /&gt;        echo &#39;Starting process accounting&#39;&lt;br /&gt;        /usr/lib/acct/startup&lt;br /&gt;        ;;&lt;br /&gt;&lt;br /&gt;    &lt;br /&gt;&lt;br /&gt;&#39;stop&#39;)&lt;br /&gt;&lt;br /&gt;        echo &#39;Stopping process accounting&#39;&lt;br /&gt;        /usr/lib/acct/shutacct&lt;br /&gt;        ;;&lt;br /&gt;&lt;br /&gt;    &lt;br /&gt;&lt;br /&gt;*)&lt;br /&gt;&lt;br /&gt;        echo &quot;Usage: $0 { start | stop }&quot;&lt;br /&gt;        exit 1&lt;br /&gt;        ;;&lt;br /&gt;&lt;br /&gt;esac&lt;br /&gt;&lt;br /&gt;exit 0&lt;br /&gt;&lt;br /&gt;The above legacy init script typically is simply a case statement that handles at least 2 arguments: start and stop. Very often these scripts will have other options like &quot;status&quot;, &quot;restart&quot;, &quot;refresh&quot; and others. &lt;br /&gt;&lt;br /&gt;These script are stored in /etc/init.d. They are then symlinked into various RC directories, 1 directory per run-level the most commonly used being /etc/rc2.d and /etc/rc3.d . Init scripts symlinked into these directories are prefixed with either a capital S for &quot;Start&quot; or K for &quot;Kill&quot;, followed by two numbers. When a system is booted scripts in these run-level directories are run if they start with a S and sequentially based on the two digits, so S00whatever is run first, then S01something, so on and so forth. This is why user added scripts tend to be named S99something, to ensure that they run last. If you have two scripts with the same digits (S99apache and S99bind) thats fine.&lt;br /&gt;&lt;br /&gt;So lets say you want /etc/init.d/cswapache2 to start at boot, you&#39;d do this:&lt;br /&gt;&lt;br /&gt;Code:&lt;br /&gt;&lt;br /&gt;# ln -s /etc/init.d/cswapache2 /etc/rc3.d/S99cswapache2&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;In a like manner, if something is already set to run at boot but you don&#39;t want it to, you can either rename the script so it doesn&#39;t begin with a capital S or just delete the symlink.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;With SMF we start to look at our applications and daemons as services. Using the svcs command we can view running services, if you add the &quot;-a&quot; option it&#39;ll show you all services running or not.&lt;br /&gt;&lt;br /&gt;Code:&lt;br /&gt;&lt;br /&gt;$ svcs&lt;br /&gt;&lt;br /&gt;STATE          STIME    FMRI&lt;br /&gt;&lt;br /&gt;legacy_run     Nov_19   lrc:/etc/rc2_d/S20sysetup&lt;br /&gt;&lt;br /&gt;legacy_run     Nov_19   lrc:/etc/rc2_d/S72autoinstall&lt;br /&gt;&lt;br /&gt;legacy_run     Nov_19   lrc:/etc/rc2_d/S73cachefs_daemon&lt;br /&gt;&lt;br /&gt;legacy_run     Nov_19   lrc:/etc/rc2_d/S85cswsaslauthd&lt;br /&gt;&lt;br /&gt;legacy_run     Nov_19   lrc:/etc/rc2_d/S89PRESERVE&lt;br /&gt;&lt;br /&gt;legacy_run     Nov_19   lrc:/etc/rc2_d/S98deallocate&lt;br /&gt;&lt;br /&gt;legacy_run     Nov_19   lrc:/etc/rc3_d/S50cswapache2&lt;br /&gt;&lt;br /&gt;online         Nov_19   svc:/system/svc/restarter:default&lt;br /&gt;&lt;br /&gt;online         Nov_19   svc:/system/filesystem/root:default&lt;br /&gt;&lt;br /&gt;online         Nov_19   svc:/network/loopback:default&lt;br /&gt;&lt;br /&gt;...&lt;br /&gt;&lt;br /&gt;online         10:20:09 svc:/network/nfs/cbd:default&lt;br /&gt;&lt;br /&gt;online         10:20:09 svc:/network/nfs/nlockmgr:default&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Here we can see the legacy init scripts that are running, and a few of the SMF services that are online, as well as when they last changed state (ie: started). You&#39;ll notice that each service has an identifying &quot;FMRI&quot; (Fault Management Resource Identifier) which is used by other Solaris frameworks such the Fault Management Architecture (FMA).&lt;br /&gt;&lt;br /&gt;Dealing with services is easy. We can use the svcadm command to &quot;enable&quot;, &quot;disable&quot;, &quot;refresh&quot;, &quot;restart&quot;, or otherwise change the state of a given service.&lt;br /&gt;&lt;br /&gt;Code:&lt;br /&gt;&lt;br /&gt;$ svcs -a | grep -i mysql&lt;br /&gt;&lt;br /&gt;disabled       Nov_17   svc:/network/cswmysql5:default&lt;br /&gt;&lt;br /&gt;$ svcadm enable svc:/network/cswmysql5:default&lt;br /&gt;&lt;br /&gt;$ svcs -a | grep -i mysql&lt;br /&gt;&lt;br /&gt;online         16:54:36 svc:/network/cswmysql5:default&lt;br /&gt;&lt;br /&gt;$ svcadm restart svc:/network/cswmysql5:default&lt;br /&gt;&lt;br /&gt;$ date&lt;br /&gt;&lt;br /&gt;Tue Nov 21 16:55:26 PST 2006&lt;br /&gt;&lt;br /&gt;$ svcs -a | grep -i mysql&lt;br /&gt;&lt;br /&gt;online         16:55:27 svc:/network/cswmysql5:default&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;In this example above I looked for any MySQL services and found network/cswmysql5 , so I enabled it, verified that it was online, then restarted it and checked again. Notice that the time at which it was started is displayed.&lt;br /&gt;&lt;br /&gt;Now lets see one way in which SMF is superior to legacy init scripts. When SMF starts something it has a &quot;contract&quot; for that service. That contract keeps track of whats running for any given service. Using the &quot;-p&quot; option we can see what processes are part of a services contract and take advantage of that intellegance.&lt;br /&gt;&lt;br /&gt;Code:&lt;br /&gt;&lt;br /&gt;$ svcs -p network/cswmysql5&lt;br /&gt;&lt;br /&gt;STATE          STIME    FMRI&lt;br /&gt;&lt;br /&gt;online         16:55:27 svc:/network/cswmysql5:default&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;               16:55:27    28938 mysqld_safe&lt;br /&gt;               16:55:27    29004 mysqld&lt;br /&gt;&lt;br /&gt;$ kill -9 29004&lt;br /&gt;&lt;br /&gt;$ svcs -p network/cswmysql5&lt;br /&gt;&lt;br /&gt;STATE          STIME    FMRI&lt;br /&gt;&lt;br /&gt;online*        17:00:01 svc:/network/cswmysql5:default&lt;br /&gt;               16:55:27    28938 mysqld_safe&lt;br /&gt;               17:00:01    29228 mysqld&lt;br /&gt;&lt;br /&gt;$ mysql -u mysql&lt;br /&gt;&lt;br /&gt;...&lt;br /&gt;&lt;br /&gt;mysql&gt; \q&lt;br /&gt;&lt;br /&gt;Bye&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Notice here that I used svcs -p to list the processes associated with my MySQL5 service. Then I brutally killed mysqld and faster than I can blink the proccess was restarted! You can see that represented by the &quot;STIME&quot; for mysqld. The asterisk (&quot;online*&quot;) indicates that the service is currently in a transistion state, in this case transitioning to online, but as you can see MySQL is already back in action.&lt;br /&gt;&lt;br /&gt;But SMF isn&#39;t restarting thing in brain-dead mode like an inittab, we can define thresholds reguarding restarts. For instance, if SMF restarts a service more than 3 times in 60 seconds, something probly very wrong and it should stop attempting it. At that point it&#39;ll put the service in a &quot;maintance&quot; mode, and it will stay that way until you clear the state with svcadm clear some/service .&lt;br /&gt;&lt;br /&gt;Lets look at an example of something broken trying to start. I&#39;m going to break MySQL and then try to start it...&lt;br /&gt;&lt;br /&gt;Code:&lt;br /&gt;&lt;br /&gt;$ mv  /opt/csw/mysql5/var/ /opt/csw/mysql5/xxx-var/&lt;br /&gt;&lt;br /&gt;$ svcadm enable network/cswmysql5&lt;br /&gt;&lt;br /&gt;$ svcs network/cswmysql5&lt;br /&gt;&lt;br /&gt;STATE          STIME    FMRI&lt;br /&gt;&lt;br /&gt;maintenance    17:29:01 svc:/network/cswmysql5:default&lt;br /&gt;&lt;br /&gt;$ svcs -vx&lt;br /&gt;&lt;br /&gt;svc:/network/cswmysql5:default (?)&lt;br /&gt;&lt;br /&gt;&lt;br /&gt; State: maintenance since Tue Nov 21 17:29:01 2006&lt;br /&gt;&lt;br /&gt;Reason: Restarting too quickly.&lt;br /&gt;   See: http://sun.com/msg/SMF-8000-L5&lt;br /&gt;   See: /var/svc/log/network-cswmysql5:default.log&lt;br /&gt;&lt;br /&gt;Impact: This service is not running.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;So I moved MySQL&#39;s data directory, obviously it can&#39;t start without it. When I enable the service it ends up in &quot;maintenance&quot;. Using SMF&#39;s most magical command svcs -vx we can see a listing of all services that failed to start, why they failed to start, some information about them, the log location, all dependencies of that service that can&#39;t start as a result, and even a URL to a page that&#39;ll tell us more!&lt;br /&gt;&lt;br /&gt;Now lets resolve the issue and bring the service back online:&lt;br /&gt;&lt;br /&gt;Code:&lt;br /&gt;&lt;br /&gt;$ mv /opt/csw/mysql5/xxx-var/ /opt/csw/mysql5/var/&lt;br /&gt;&lt;br /&gt;$ svcs network/cswmysql5&lt;br /&gt;&lt;br /&gt;STATE          STIME    FMRI&lt;br /&gt;&lt;br /&gt;maintenance    17:29:01 svc:/network/cswmysql5:default&lt;br /&gt;&lt;br /&gt;$ svcadm clear network/cswmysql5&lt;br /&gt;&lt;br /&gt;$ svcs network/cswmysql5&lt;br /&gt;&lt;br /&gt;STATE          STIME    FMRI&lt;br /&gt;&lt;br /&gt;online         17:32:57 svc:/network/cswmysql5:default&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;The usefulness of the svcs -vx command can not be overstated. The first thing I run when logging into any Solaris 10 or OpenSolaris machine is this command.&lt;br /&gt;&lt;br /&gt;So how do you actually use SMF with your own service?&lt;br /&gt;&lt;br /&gt;SMF Services are defined in XML Manifests. These manifests describe how to start, stop, restart, and refresh (reload the configuration) your application, what dependancies it has, various thresholds, as well as various meta-data that may be useful such as man pages that apply to that service. In addition to the manifest, scripts just like your legacy init scripts can be used which we call methods , or &quot;method scripts&quot;.&lt;br /&gt;&lt;br /&gt;Service configuration changes can be made by using the svccfg (&quot;Service Config&quot;) tool. The most common uses of this command are to import or export a manifest. For instance, I&#39;m curious what the manifest for that MySQL5 service looks like:&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Code:&lt;br /&gt;&lt;br /&gt;$ svccfg export network/cswmysql5&lt;br /&gt;&lt;br /&gt;To view the code refer &lt;a href=&quot;http://pastebin.com/yRqeMKzi&quot;&gt;http://pastebin.com/yRqeMKzi&lt;/a&gt;&lt;br /&gt;&lt;?xml version=&#39;1.0&#39;?&gt;&lt;br /&gt;&lt;br /&gt;&lt;!DOCTYPE service_bundle SYSTEM &#39;/usr/share/lib/xml/dtd/service_bundle.dtd.1&#39;&gt;&lt;br /&gt;&lt;br /&gt;&lt;service_bundle type=&#39;manifest&#39; name=&#39;export&#39;&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;  &lt;service name=&#39;network/cswmysql5&#39; type=&#39;service&#39; version=&#39;0&#39;&gt;&lt;br /&gt;    &lt;create_default_instance enabled=&#39;true&#39;/&gt;&lt;br /&gt;    &lt;single_instance/&gt;&lt;br /&gt;    &lt;dependency name=&#39;fs&#39; grouping=&#39;require_all&#39; restart_on=&#39;none&#39; type=&#39;service&#39;&gt;&lt;br /&gt;      &lt;service_fmri value=&#39;svc:/system/filesystem/local&#39;/&gt;&lt;br /&gt;    &lt;/dependency&gt;&lt;br /&gt;    &lt;dependency name=&#39;net&#39; grouping=&#39;require_all&#39; restart_on=&#39;none&#39; type=&#39;service&#39;&gt;&lt;br /&gt;      &lt;service_fmri value=&#39;svc:/network/loopback&#39;/&gt;&lt;br /&gt;    &lt;/dependency&gt;&lt;br /&gt;    &lt;dependent name=&#39;cswmysql5_multi-user&#39; restart_on=&#39;none&#39; grouping=&#39;optional_all&#39;&gt;&lt;br /&gt;      &lt;service_fmri value=&#39;svc:/milestone/multi-user&#39;/&gt;&lt;br /&gt;    &lt;/dependent&gt;&lt;br /&gt;    &lt;exec_method name=&#39;start&#39; type=&#39;method&#39; exec=&#39;/opt/csw/lib/svc/method/svc-mysql5 start&#39; timeout_seconds=&#39;60&#39;&gt;&lt;br /&gt;      &lt;method_context/&gt;&lt;br /&gt;    &lt;/exec_method&gt;&lt;br /&gt;    &lt;exec_method name=&#39;stop&#39; type=&#39;method&#39; exec=&#39;:kill&#39; timeout_seconds=&#39;60&#39;&gt;&lt;br /&gt;      &lt;method_context/&gt;&lt;br /&gt;    &lt;/exec_method&gt;&lt;br /&gt;    &lt;exec_method name=&#39;restart&#39; type=&#39;method&#39; exec=&#39;/opt/csw/lib/svc/method/svc-mysql5 restart&#39; timeout_seconds=&#39;60&#39;&gt;&lt;br /&gt;      &lt;method_context/&gt;&lt;br /&gt;    &lt;/exec_method&gt;&lt;br /&gt;  &lt;/service&gt;&lt;br /&gt;&lt;br /&gt;&lt;/service_bundle&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;That probly looks really intimidating at first glance, but its really not so bad if you just break it down. First we define our dependencies, for instance MySQL is dependent on the network loopback service and the local filesystems service. There are 3 &quot;exec_methods&quot; which define the methods for start, stop, and restart. If you can start your app or daemon in just a single line then you don&#39;t need an external method script, but in the case of this service it opts for a script. Notice the &quot;stop&quot; method uses an SMF shortcut which just kills the processes rather than use a script or command.&lt;br /&gt;&lt;br /&gt;This is only a very simple example, you can put lots more information in there, but its pretty simple XML when you just break it down.&lt;br /&gt;&lt;br /&gt;When you create a new SMF Manifest, you simple put the XML in a file and use svccfg import my_service.xml to import it. </content><link rel='replies' type='application/atom+xml' href='http://linuxscoop.blogspot.com/feeds/1289062429044450039/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://linuxscoop.blogspot.com/2011/08/setting-up-automatic-startup-script-for.html#comment-form' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/1289062429044450039'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/1289062429044450039'/><link rel='alternate' type='text/html' href='http://linuxscoop.blogspot.com/2011/08/setting-up-automatic-startup-script-for.html' title='Setting up automatic startup script for Solaris 10 Update 9'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1019359938654970995.post-8002729780121946000</id><published>2011-07-21T05:54:00.000-07:00</published><updated>2011-07-21T06:11:10.151-07:00</updated><title type='text'>How to setup OpenManage on ESX 4.1.0</title><content type='html'>&lt;a onblur=&quot;try {parent.deselectBloggerImageGracefully();} catch(e) {}&quot; href=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEih3ta1h3QoASnht4Ba3IS6MSDlmSs6Mlc6vfzD-HQzsk1kElL6E8ZiQ7pCLtDbvP_fLpLRUF_DuMsfbn049V_tCAs5ABketDN7QErJo4llUswqsdo2OmY3-bl94UhrR1SZHyYuB1FcTWYh/s1600/dellopenmage.bmp&quot;&gt;&lt;img style=&quot;float:left; margin:0 10px 10px 0;cursor:pointer; cursor:hand;width: 320px; height: 162px;&quot; src=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEih3ta1h3QoASnht4Ba3IS6MSDlmSs6Mlc6vfzD-HQzsk1kElL6E8ZiQ7pCLtDbvP_fLpLRUF_DuMsfbn049V_tCAs5ABketDN7QErJo4llUswqsdo2OmY3-bl94UhrR1SZHyYuB1FcTWYh/s320/dellopenmage.bmp&quot; border=&quot;0&quot; alt=&quot;&quot;id=&quot;BLOGGER_PHOTO_ID_5631792463760074114&quot; /&gt;&lt;/a&gt;&lt;br /&gt;Dell OpenManage is a suite of system management applications for managing Dell PowerEdge servers. Today I carried out my day with an aim to see how OpenManage could be setup on top of ESX 4.1. I have ESX 4.1 build on Dell PowerEdge 2970 hardware.&lt;br /&gt;I followed the following steps:&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;1. Install ESX 4.1.0 build on your Dell hardware. Enable ssh and firewall as shown below:&lt;br /&gt;&lt;br /&gt;#vi /etc/ssh/sshd_config&lt;br /&gt;&lt;br /&gt;PermitRootLogin yes&lt;br /&gt;&lt;br /&gt;#esxcfg-firewall --allowOutgoing --allowIncoming&lt;br /&gt;&lt;br /&gt;2. Download OpenManage Package from http://ftp.dell.com/sysman/OM-SrvAdmin-Dell-Web-LX-6.3.0-2075.ESX41.i386_A00.12.tar.gz and scp to ESX server(You can use wget alternative command to put it under ESX straight)&lt;br /&gt;&lt;br /&gt;3.Run the followind command:&lt;br /&gt;&lt;br /&gt;#mkdir /tmp/openmanage &lt;br /&gt;#cd /tmp/openmanage &lt;br /&gt;#tar xvzf /path/to/OM-SrvAdmin-Dell-Web-LX-6.3.0-2075.ESX41.i386_A00.12.tar.gz &lt;br /&gt;#cd linux/supportscripts/ &lt;br /&gt;&lt;br /&gt;[root@vmqa021-km-s2970 supportscripts]# ./srvadmin-install.sh -w -r -s&lt;br /&gt;Installing the selected packages.&lt;br /&gt;&lt;br /&gt;warning: libsmbios-2.2.19-5.1.vmw41.i386.rpm: Header V3 DSA signature: NOKEY, &lt;br /&gt;&lt;br /&gt;key ID 23b66a9d&lt;br /&gt;warning: smbios-utils-bin-2.2.19-5.1.vmw41.i386.rpm: Header V3 DSA signature: &lt;br /&gt;&lt;br /&gt;NOKEY, key ID 23b66a9d&lt;br /&gt;warning: libsmbios-2.2.19-5.1.vmw41.i386.rpm: Header V3 DSA signature: NOKEY, &lt;br /&gt;&lt;br /&gt;key ID 23b66a9d&lt;br /&gt;Preparing...                ########################################### &lt;br /&gt;&lt;br /&gt;[100%]&lt;br /&gt;   1:libsmbios              ########################################### [ &lt;br /&gt;&lt;br /&gt;50%]&lt;br /&gt;/sbin/ldconfig: /usr/lib/libkrb4.so.2 is not a symbolic link&lt;br /&gt;&lt;br /&gt;/sbin/ldconfig: /usr/lib64/libkrb4.so.2 is not a symbolic link&lt;br /&gt;&lt;br /&gt;   2:smbios-utils-bin       ########################################### &lt;br /&gt;&lt;br /&gt;[100%]&lt;br /&gt;warning: &lt;br /&gt;&lt;br /&gt;/tmp/openmanage/linux/RPMS/supportRPMS/srvadmin/ESX41/i386/../../../opensourc&lt;br /&gt;&lt;br /&gt;e-components/ESX41/i386/libwsman1-2.2.1-1.2.vmw41.i386.rpm: Header V3 DSA &lt;br /&gt;&lt;br /&gt;signature: NOKEY, key ID 23b66a9d&lt;br /&gt;warning: &lt;br /&gt;&lt;br /&gt;/tmp/openmanage/linux/RPMS/supportRPMS/srvadmin/ESX41/i386/../../../opensourc&lt;br /&gt;&lt;br /&gt;e-components/ESX41/i386/openwsman-client-2.2.1-1.2.vmw41.i386.rpm: Header V3 &lt;br /&gt;&lt;br /&gt;DSA signature: NOKEY, key ID 23b66a9d&lt;br /&gt;warning: &lt;br /&gt;&lt;br /&gt;/tmp/openmanage/linux/RPMS/supportRPMS/srvadmin/ESX41/i386/../../../opensourc&lt;br /&gt;&lt;br /&gt;e-components/ESX41/i386/libwsman1-2.2.1-1.2.vmw41.i386.rpm: Header V3 DSA &lt;br /&gt;&lt;br /&gt;signature: NOKEY, key ID 23b66a9d&lt;br /&gt;Preparing...                ########################################### &lt;br /&gt;&lt;br /&gt;[100%]&lt;br /&gt;   1:libwsman1              ########################################### [ &lt;br /&gt;&lt;br /&gt;50%]&lt;br /&gt;/sbin/ldconfig: /usr/lib/libkrb4.so.2 is not a symbolic link&lt;br /&gt;&lt;br /&gt;/sbin/ldconfig: /usr/lib64/libkrb4.so.2 is not a symbolic link&lt;br /&gt;&lt;br /&gt;   2:openwsman-client       ########################################### &lt;br /&gt;&lt;br /&gt;[100%]&lt;br /&gt;/sbin/ldconfig: /usr/lib/libkrb4.so.2 is not a symbolic link&lt;br /&gt;&lt;br /&gt;/sbin/ldconfig: /usr/lib64/libkrb4.so.2 is not a symbolic link&lt;br /&gt;&lt;br /&gt;warning: srvadmin-argtable2-6.3.0-9.1.vmw41.i386.rpm: Header V3 DSA &lt;br /&gt;&lt;br /&gt;signature: NOKEY, key ID 23b66a9d&lt;br /&gt;Preparing...                ########################################### &lt;br /&gt;&lt;br /&gt;[100%]&lt;br /&gt;   1:srvadmin-storelib      ########################################### [  &lt;br /&gt;&lt;br /&gt;4%]&lt;br /&gt;/sbin/ldconfig: /usr/lib/libkrb4.so.2 is not a symbolic link&lt;br /&gt;&lt;br /&gt;/sbin/ldconfig: /usr/lib64/libkrb4.so.2 is not a symbolic link&lt;br /&gt;&lt;br /&gt;   2:srvadmin-hapi          ########################################### [  &lt;br /&gt;&lt;br /&gt;9%]&lt;br /&gt;   3:srvadmin-sysfsutils    ########################################### [ &lt;br /&gt;&lt;br /&gt;13%]&lt;br /&gt;   4:srvadmin-megalib       ########################################### [ &lt;br /&gt;&lt;br /&gt;17%]&lt;br /&gt;/sbin/ldconfig: /usr/lib/libkrb4.so.2 is not a symbolic link&lt;br /&gt;&lt;br /&gt;/sbin/ldconfig: /usr/lib64/libkrb4.so.2 is not a symbolic link&lt;br /&gt;&lt;br /&gt;   5:srvadmin-libxslt       ########################################### [ &lt;br /&gt;&lt;br /&gt;22%]&lt;br /&gt;/sbin/ldconfig: /usr/lib/libkrb4.so.2 is not a symbolic link&lt;br /&gt;&lt;br /&gt;/sbin/ldconfig: /usr/lib64/libkrb4.so.2 is not a symbolic link&lt;br /&gt;&lt;br /&gt;   6:srvadmin-xmlsup        ########################################### [ &lt;br /&gt;&lt;br /&gt;26%]&lt;br /&gt;ldconfig: /usr/lib/libkrb4.so.2 is not a symbolic link&lt;br /&gt;&lt;br /&gt;ldconfig: /usr/lib64/libkrb4.so.2 is not a symbolic link&lt;br /&gt;&lt;br /&gt;   7:srvadmin-argtable2     ########################################### [ &lt;br /&gt;&lt;br /&gt;30%]&lt;br /&gt;/sbin/ldconfig: /usr/lib/libkrb4.so.2 is not a symbolic link&lt;br /&gt;&lt;br /&gt;/sbin/ldconfig: /usr/lib64/libkrb4.so.2 is not a symbolic link&lt;br /&gt;&lt;br /&gt;   8:srvadmin-omilcore      ########################################### [ &lt;br /&gt;&lt;br /&gt;35%]&lt;br /&gt;ldconfig: /usr/lib/libkrb4.so.2 is not a symbolic link&lt;br /&gt;&lt;br /&gt;ldconfig: /usr/lib64/libkrb4.so.2 is not a symbolic link&lt;br /&gt;&lt;br /&gt;     **********************************************************&lt;br /&gt;     After the install process completes, you may need&lt;br /&gt;     to log out and then log in again to reset the PATH&lt;br /&gt;     variable to access the Dell OpenManage CLI utilities&lt;br /&gt;&lt;br /&gt;     **********************************************************&lt;br /&gt;   9:srvadmin-deng          ########################################### [ &lt;br /&gt;&lt;br /&gt;39%]&lt;br /&gt;  10:srvadmin-omcommon      ########################################### [ &lt;br /&gt;&lt;br /&gt;43%]&lt;br /&gt;  11:srvadmin-isvc          ########################################### [ &lt;br /&gt;&lt;br /&gt;48%]&lt;br /&gt;  12:srvadmin-omacore       ########################################### [ &lt;br /&gt;&lt;br /&gt;52%]&lt;br /&gt;  13:srvadmin-rac-components########################################### [ &lt;br /&gt;&lt;br /&gt;57%]&lt;br /&gt;ldconfig: /usr/lib/libkrb4.so.2 is not a symbolic link&lt;br /&gt;&lt;br /&gt;ldconfig: /usr/lib64/libkrb4.so.2 is not a symbolic link&lt;br /&gt;&lt;br /&gt;  14:srvadmin-racdrsc       ########################################### [ &lt;br /&gt;&lt;br /&gt;61%]&lt;br /&gt;ldconfig: /usr/lib/libkrb4.so.2 is not a symbolic link&lt;br /&gt;&lt;br /&gt;ldconfig: /usr/lib64/libkrb4.so.2 is not a symbolic link&lt;br /&gt;&lt;br /&gt;  15:srvadmin-racadm5       ########################################### [ &lt;br /&gt;&lt;br /&gt;65%]&lt;br /&gt;  16:srvadmin-racadm4       ########################################### [ &lt;br /&gt;&lt;br /&gt;70%]&lt;br /&gt;ldconfig: /usr/lib/libkrb4.so.2 is not a symbolic link&lt;br /&gt;&lt;br /&gt;ldconfig: /usr/lib64/libkrb4.so.2 is not a symbolic link&lt;br /&gt;&lt;br /&gt;  17:srvadmin-smcommon      ########################################### [ &lt;br /&gt;&lt;br /&gt;74%]&lt;br /&gt;  18:srvadmin-jre           ########################################### [ &lt;br /&gt;&lt;br /&gt;78%]&lt;br /&gt;  19:srvadmin-smweb         ########################################### [ &lt;br /&gt;&lt;br /&gt;83%]&lt;br /&gt;  20:srvadmin-cm            ########################################### [ &lt;br /&gt;&lt;br /&gt;87%]&lt;br /&gt;  21:srvadmin-iws           ########################################### [ &lt;br /&gt;&lt;br /&gt;91%]&lt;br /&gt;  22:srvadmin-storage       ########################################### [ &lt;br /&gt;&lt;br /&gt;96%]&lt;br /&gt;  23:srvadmin-storage-popula########################################### &lt;br /&gt;&lt;br /&gt;[100%]&lt;br /&gt;ldconfig: /usr/lib/libkrb4.so.2 is not a symbolic link&lt;br /&gt;&lt;br /&gt;ldconfig: /usr/lib64/libkrb4.so.2 is not a symbolic link&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;#su - &lt;br /&gt;&lt;br /&gt;[root@vmqa021-km-s2970 ~]# srvadmin-services.sh start&lt;br /&gt;Starting Systems Management Device Drivers:&lt;br /&gt;Starting dell_rbu:                                         [  OK  ]&lt;br /&gt;Starting ipmi driver: Already started                      [  OK  ]&lt;br /&gt;Starting snmpd:                                            [  OK  ]&lt;br /&gt;Starting Systems Management Data Engine:&lt;br /&gt;Starting dsm_sa_datamgrd:                                  [  OK  ]&lt;br /&gt;Starting dsm_sa_eventmgrd:                                 [  OK  ]&lt;br /&gt;Starting dsm_sa_snmpd:                                     [  OK  ]&lt;br /&gt;Starting DSM SA Shared Services:                           [  OK  ]&lt;br /&gt;Starting DSM SA Connection Service:                        [  OK  ]&lt;br /&gt;[root@vmqa021-km-s2970 ~]#&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;#esxcfg-firewall -o 1311,tcp,in,OpenManage &lt;br /&gt;#cd /tmp &lt;br /&gt;#rm -rf openmanage/ &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;There you go. Shoot out https://10.112.172.55:1311 and there you see OpenManage Page.&lt;br /&gt;&lt;br /&gt;Till then, Enjoy Maadi !!!</content><link rel='replies' type='application/atom+xml' href='http://linuxscoop.blogspot.com/feeds/8002729780121946000/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://linuxscoop.blogspot.com/2011/07/how-to-setup-openmanage-on-esx-410.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/8002729780121946000'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/8002729780121946000'/><link rel='alternate' type='text/html' href='http://linuxscoop.blogspot.com/2011/07/how-to-setup-openmanage-on-esx-410.html' title='How to setup OpenManage on ESX 4.1.0'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEih3ta1h3QoASnht4Ba3IS6MSDlmSs6Mlc6vfzD-HQzsk1kElL6E8ZiQ7pCLtDbvP_fLpLRUF_DuMsfbn049V_tCAs5ABketDN7QErJo4llUswqsdo2OmY3-bl94UhrR1SZHyYuB1FcTWYh/s72-c/dellopenmage.bmp" height="72" width="72"/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1019359938654970995.post-1256135196037361982</id><published>2011-06-09T11:02:00.000-07:00</published><updated>2011-06-09T11:06:04.874-07:00</updated><title type='text'>How to inject driver into Linux Image ISO?</title><content type='html'>EXTRACT CD:&lt;br /&gt;&lt;br /&gt;1) Boot up a Linux Box (I used WhiteBox Enterprise with 2.4.21-27 kern)&lt;br /&gt;2) Insert CD into CDROM&lt;br /&gt;3) mkdir /cdiso&lt;br /&gt;4) cp -av /mnt/cdrom/* /cdiso&lt;br /&gt;&lt;br /&gt;EXTRACT and EDIT INITRD.IMG (The Linux Filesystem)&lt;br /&gt;&lt;br /&gt;5) mkdir /cdinitimg&lt;br /&gt;6) find the initrd.gz or initrd.img in /cdiso&lt;br /&gt;7) gunzip -c /cdiso/isolinux/initrd.img &gt; /cdinitimg/initrd.img&lt;br /&gt;- believe it or not the image is compressed&lt;br /&gt;8) cd /cdinitimg&lt;br /&gt;9) mdkir point&lt;br /&gt;10) mount initrd.img point -o loop&lt;br /&gt;11) mkdir /cdimgextract&lt;br /&gt;12) cp -av /cdinitimg/point/* /cdimgextract&lt;br /&gt;13) umount /cdinitimg/point&lt;br /&gt;14) rm -rf /cdinitimg&lt;br /&gt;15) make any changes you need to the initrd.img in /cdimgextract&lt;br /&gt;&lt;br /&gt;REMAKE MODIFIED INITRD.IMG&lt;br /&gt;&lt;br /&gt;16) mkdir /cdinitrd&lt;br /&gt;17) dd if=/dev/zero of=initrd.img bs=1k count=60960&lt;br /&gt;18) mke2fs -i 1024 -b 1024 -m 5 -F -v initrd.img&lt;br /&gt;19) mount initrd.img cdinitrd -t ext2 -o loop&lt;br /&gt;20) cp -av /cdimgextract/* /cdinitrd&lt;br /&gt;21) umount /cdinitrd&lt;br /&gt;22) gzip --best initrd.img&lt;br /&gt;23) cp initrd.img /cdiso/isolinux/&lt;br /&gt;24) rm -rf /cdinitrd&lt;br /&gt;25) rm -rf /cdimgextract&lt;br /&gt;&lt;br /&gt;REMAKE MODIFIED ISO&lt;br /&gt;&lt;br /&gt;26) cd /cdiso&lt;br /&gt;27) use this shell script:&lt;br /&gt;-note: you may have to edit it a little to fit your ISO.&lt;br /&gt;&lt;br /&gt;#!/bin/bash&lt;br /&gt;# make the new iso and put in root.&lt;br /&gt;mkisofs -o /new.iso -b isolinux/isolinux.bin \&lt;br /&gt;-c isolinux/boot.cat -no-emul-boot -boot-load-size 4 \&lt;br /&gt;-boot-info-table -J -R -V disks .&lt;br /&gt;#&lt;br /&gt;&lt;br /&gt;28) now you have a new ISO named new.iso in your / directory&lt;br /&gt;&lt;br /&gt;BURN THE NEW ISO IMAGE&lt;br /&gt;&lt;br /&gt;29) eject the old cd, and pop in a blank&lt;br /&gt;- make sure you have cdrecord&lt;br /&gt;30) cdrecord -v -pad speed=1 dev=0,0,0 /new.iso&lt;br /&gt;&lt;br /&gt;NOTE: For the record, I had to edit a RHEL 6.0 Beta CD to add pvscsci driver</content><link rel='replies' type='application/atom+xml' href='http://linuxscoop.blogspot.com/feeds/1256135196037361982/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://linuxscoop.blogspot.com/2011/06/how-to-inject-driver-into-linux-image.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/1256135196037361982'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/1256135196037361982'/><link rel='alternate' type='text/html' href='http://linuxscoop.blogspot.com/2011/06/how-to-inject-driver-into-linux-image.html' title='How to inject driver into Linux Image ISO?'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1019359938654970995.post-4456408991254341135</id><published>2011-05-20T03:02:00.000-07:00</published><updated>2011-05-20T03:09:36.697-07:00</updated><title type='text'>Booting Solaris Systems to Either the 64-Bit Kernel or the 32-Bit Kernel</title><content type='html'>A common questions which I came across huge number of times while exploring the OpenSolaris forum - How do I configure the system to boot a 32-bit kernel or 64 bit kernel?. &lt;br /&gt;&lt;br /&gt;This lead me to include it on my blog so as to help my friends with 32 bit and 64 bit availability of Solaris 10. &lt;br /&gt;Here is the way to do that:&lt;br /&gt;&lt;br /&gt;Booting into 32 bit:&lt;br /&gt;&lt;br /&gt;You searched for Solaris 10 and just got to see a single ISO. No issues.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Log in as root and use the eeprom command to set the boot-file parameter to the 32-bit kernel:&lt;br /&gt;&lt;br /&gt; # /usr/sbin/eeprom  boot-file=&quot;kernel/unix&quot;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;The next time the system is rebooted, the 32-bit kernel will load.&lt;br /&gt;&lt;br /&gt;To confirm what kernel your system is running now:&lt;br /&gt;&lt;br /&gt;Run the following command:&lt;br /&gt;&lt;br /&gt;       $ /usr/bin/isainfo -kv&lt;br /&gt;       64-bit sparcv9 kernel modules&lt;br /&gt;&lt;br /&gt;The 64-bit sparcv9 output indicates the system is running the 64-bit Solaris kernel.&lt;br /&gt;Else, it is running 32 bit.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Hope this quick guide makes someone&#39;s day.</content><link rel='replies' type='application/atom+xml' href='http://linuxscoop.blogspot.com/feeds/4456408991254341135/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://linuxscoop.blogspot.com/2011/05/booting-solaris-systems-to-either-64.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/4456408991254341135'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/4456408991254341135'/><link rel='alternate' type='text/html' href='http://linuxscoop.blogspot.com/2011/05/booting-solaris-systems-to-either-64.html' title='Booting Solaris Systems to Either the 64-Bit Kernel or the 32-Bit Kernel'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1019359938654970995.post-902132339545343631</id><published>2011-04-30T20:05:00.000-07:00</published><updated>2011-04-30T20:12:07.026-07:00</updated><title type='text'>How do I bind NIC interrupts to selected CPU?</title><content type='html'>I read this interesting mailing thread and want to share with all the followers and commuters searching for the solution.&lt;br /&gt;&lt;br /&gt;I have a 4 Quad server, am trying to bind NIC eth0 interrupt(s) to CPU4 and&lt;br /&gt;CPU5. As of now, my eth0 is found bind to all the 8&#39;s.&lt;br /&gt;&lt;br /&gt;grep eth0 /proc/interrupts | awk &#39;{print $NF}&#39; | sort&lt;br /&gt;&lt;br /&gt;eth0-0&lt;br /&gt;eth0-1&lt;br /&gt;eth0-2&lt;br /&gt;eth0-3&lt;br /&gt;eth0-4&lt;br /&gt;eth0-5&lt;br /&gt;eth0-6&lt;br /&gt;eth0-7&lt;br /&gt;&lt;br /&gt;How to move ahead?&lt;br /&gt;&lt;br /&gt;Solution: Follow these steps to get it done.&lt;br /&gt;&lt;br /&gt;As I am using Broadcom card(bnx2), I am going to run  this command and reboot my machine.&lt;br /&gt;&lt;br /&gt;Open the terminal:&lt;br /&gt;&lt;br /&gt;echo &quot;options bnx2 disable_msi=1&quot; &gt; /etc/modprobe.d/bnx2.conf&lt;br /&gt;&lt;br /&gt;then reboot, after you&#39;ll only see one irq for eth0.&lt;br /&gt;&lt;br /&gt;Next, run this command:&lt;br /&gt;&lt;br /&gt;echo cpumask &gt; /proc/irq/IRQ-OF-ETH0-0/smp_affinity&lt;br /&gt;&lt;br /&gt;I believe the mask for cpu4 is 10 and cpu5 is 20.&lt;br /&gt;(don&#39;t forget to disable irqbalance)&lt;br /&gt;&lt;br /&gt;you can only bind the irqs for one nic to one core at a time.&lt;br /&gt;&lt;br /&gt;or you could do something fancy/silly with isolcpus and....&lt;br /&gt;&lt;br /&gt;isolcpus all but 4/5 so that all irqs will be scheduled on 4/5. this will&lt;br /&gt;mean that the kernel can only schedule tasks on cpu4/5.&lt;br /&gt;&lt;br /&gt;Hope it helps !!!&lt;br /&gt;then use cpusets/taskset/tuna to move all the processes off cpu 4/5...  and&lt;br /&gt;you&#39;ll have to use taskset/cpuset/tuna for every task to ensure its not&lt;br /&gt;using cpu4/5</content><link rel='replies' type='application/atom+xml' href='http://linuxscoop.blogspot.com/feeds/902132339545343631/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://linuxscoop.blogspot.com/2011/04/how-do-i-bind-nic-interrupts-to.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/902132339545343631'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/902132339545343631'/><link rel='alternate' type='text/html' href='http://linuxscoop.blogspot.com/2011/04/how-do-i-bind-nic-interrupts-to.html' title='How do I bind NIC interrupts to selected CPU?'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1019359938654970995.post-1606318404411081317</id><published>2011-04-30T19:52:00.000-07:00</published><updated>2011-04-30T20:00:48.689-07:00</updated><title type='text'>How to transfer files through Bluetooth under Ubuntu? - Part-I</title><content type='html'>Bluetooth is a specification for the use of low-power radio communications to wirelessly link phones, computers and other network devices over short distances. The name Bluetooth is borrowed from Harald Bluetooth, a king in Denmark more than 1,000 years ago. &lt;br /&gt;&lt;br /&gt;Bluetooth is the short-range networking facility that allows various items of hardware to work with each other wirelessly. For Bluetooth to work, both devices need to have Bluetooth support. Many mobile phones come with Bluetooth nowadays, and an increasing number of notebook computers do too. It’s also possible to buy very inexpensive Bluetooth USB adapters.&lt;br /&gt;&lt;br /&gt;Your PC’s Bluetooth hardware is automatically recognized under Ubuntu, and the low-level driver software is installed by default. Therefore, all you normally need to do is install the software that provides the Bluetooth functionality you require.&lt;br /&gt;&lt;br /&gt;Configuring Bluetooth&lt;br /&gt;&lt;br /&gt;When two pieces of Bluetooth-compatible hardware need to communicate on a regular basis, they can pair together. This means that they trust each other, so you don’t need to authorize every attempt at communication between the devices. Indeed, some devices won’t communicate unless they’re paired in this way.&lt;br /&gt;&lt;br /&gt;Pairing is very simple in practice and works on the principle of a shared personal ID number (PIN). The first Bluetooth device generates the PIN, and then asks the second Bluetooth device to confirm it. Once the user has typed in the PIN, the devices are paired.&lt;br /&gt;&lt;br /&gt;Pairing is easily accomplished under Ubuntu and doesn’t require any additional software. However, you will need to edit a configuration file. This only needs to be done once.&lt;br /&gt;&lt;br /&gt;Start by opening the central Bluetooth configuration file, hcid.conf, in Gedit, using superuser powers:&lt;br /&gt;&lt;br /&gt;Code:&lt;br /&gt;&lt;br /&gt;gksu gedit /etc/bluetooth/hcid.conf&lt;br /&gt;&lt;br /&gt;Look for the line that reads &quot;security user&quot;, and change it so that it reads &quot;security auto&quot;.&lt;br /&gt;&lt;br /&gt;The default PIN needed to pair with Ubuntu is 1234. For security reasons, it’s wise to change this, and the setting is contained further down in the hcid.conf file. Look for the line that reads&lt;br /&gt;&lt;br /&gt;Code:&lt;br /&gt;&lt;br /&gt;passkey &quot;1234&quot;;&lt;br /&gt;&lt;br /&gt;and replace 1234 with the number you desire. For example, if I wanted a PIN of 9435, the line would read&lt;br /&gt;&lt;br /&gt;Code:&lt;br /&gt;&lt;br /&gt;passkey &quot;9435&quot;;&lt;br /&gt;&lt;br /&gt;When you’ve finished, save the file, and close Gedit. It’s then necessary to restart the background Bluetooth service. To do this, type the following into a Terminal window (Applications -&gt; Accessores -&gt; Terminal):&lt;br /&gt;&lt;br /&gt;Code:&lt;br /&gt;&lt;br /&gt;sudo /etc/init.d/bluetooth restart&lt;br /&gt;&lt;br /&gt;Following this, I paired my Ubuntu test PC to a Nokia 6680 mobile phone. It’s easiest to initiate pairing on the phone, which should then autosense the PC’s Bluetooth connection.&lt;br /&gt;&lt;br /&gt;On my Samsung Champ, I opened the menu, and selected Connections -&gt; Bluetooth. Then I pressed the right arrow key to select Paired Devices and selected Options -&gt; New Paired Device -&gt; More Devices. This made the phone autosense my Ubuntu PC, which was identified by its hostname, followed by -0. In my case, the Ubuntu PC was identified as keir-desktop-0, and I was then prompted to enter the PIN I set earlier. Following this, the two devices were paired.&lt;br /&gt;&lt;br /&gt;In the next episode we will discuss how to transfer/receive files through bluetooth.&lt;br /&gt;Till then, bbye.</content><link rel='replies' type='application/atom+xml' href='http://linuxscoop.blogspot.com/feeds/1606318404411081317/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://linuxscoop.blogspot.com/2011/04/how-to-transfer-files-through-bluetooth.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/1606318404411081317'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/1606318404411081317'/><link rel='alternate' type='text/html' href='http://linuxscoop.blogspot.com/2011/04/how-to-transfer-files-through-bluetooth.html' title='How to transfer files through Bluetooth under Ubuntu? - Part-I'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1019359938654970995.post-5052432260844851338</id><published>2011-01-22T11:29:00.002-08:00</published><updated>2011-01-22T11:30:03.315-08:00</updated><title type='text'>Logging activity to a MySQL database</title><content type='html'>Problem&lt;br /&gt;Rather than logging accesses to your server in flat text files, you want to log the information directly to a database for easier analysis.&lt;br /&gt;&lt;br /&gt;Solution&lt;br /&gt;&lt;br /&gt;Install the latest release of mod_log_sql from http://www.outoforder.cc/projects/apache/&lt;br /&gt;mod_log_sql/ according to the modules directions (see Recipe 2.1), and then issue the following commands:&lt;br /&gt;&lt;br /&gt;# mysqladmin create apache_log&lt;br /&gt;# mysql apache_log &lt; access_log.sql # mysql apache_log mysql&gt; grant insert,create on apache_log.* to webserver@localhost identified by &#39;wwwpw&#39; ;&lt;br /&gt;&lt;br /&gt;Add the following lines to your httpd.conf file:&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;LogSQLLoginInfo mysql://webserver:wwwpw@dbmachine.example.com/apache_log&lt;br /&gt;LogSQLCreateTables on&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Then, in your VirtualHost container, add the following log directive:&lt;br /&gt;&lt;br /&gt;LogSQLTransferLogTable access_log&lt;br /&gt;&lt;br /&gt;Discussion&lt;br /&gt;&lt;br /&gt;Replace the values of webserver and wwwpw with a less guessable username and password when you run these commands.&lt;br /&gt;Consult the documentation on the referenced website to ensure that the example here reflects the version of the module that you have installed, as the configuration syntax changed with the 2.0 release of the module.</content><link rel='replies' type='application/atom+xml' href='http://linuxscoop.blogspot.com/feeds/5052432260844851338/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/logging-activity-to-mysql-database.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/5052432260844851338'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/5052432260844851338'/><link rel='alternate' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/logging-activity-to-mysql-database.html' title='Logging activity to a MySQL database'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1019359938654970995.post-7075717519894261739</id><published>2011-01-22T11:29:00.001-08:00</published><updated>2011-01-22T11:29:31.312-08:00</updated><title type='text'>Building a Centralized Logging Server</title><content type='html'>I was just hanging around blogs until I cam across one nice piece of setting up centralized Logging setup.I thought to try it out of mine and here is the output:&lt;br /&gt;&lt;br /&gt;Syslog is a fantastic facility for logging on Linux machines. Lets say you have a small number of servers, and want to log them all to one central syslog server. Here we&#39;ll describe a simple configuration.&lt;br /&gt;&lt;br /&gt;1) Setup the syslog server&lt;br /&gt;&lt;br /&gt;On the system you want to use as the syslog server, edit the file /etc/sysconf/syslog, and add &#39;-r&#39; as follows:&lt;br /&gt;&lt;br /&gt;# Options to syslogd&lt;br /&gt;# -m 0 disables &#39;MARK&#39; messages.&lt;br /&gt;# -r enables logging from remote machines&lt;br /&gt;# -x disables DNS lookups on messages recieved with -r&lt;br /&gt;# See syslogd(8) for more details&lt;br /&gt;SYSLOGD_OPTIONS=&quot;-m 0 -r&quot;&lt;br /&gt;# Options to klogd&lt;br /&gt;# -2 prints all kernel oops messages twice; once for klogd to decode, and&lt;br /&gt;# once for processing with &#39;ksymoops&#39;&lt;br /&gt;# -x disables all klogd processing of oops messages entirely&lt;br /&gt;# See klogd(8) for more details&lt;br /&gt;KLOGD_OPTIONS=&quot;-x&quot;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Initially I added -x because I thought it would use networked DNS. But as I am logging all from local servers, all of which are defined in /etc/hosts, it doesn&#39;t actually go to the network for name lookup. And, having the name of the system in the log file is nice.&lt;br /&gt;&lt;br /&gt;Now, restart syslog, and confirm that syslog is listening on port 514 (the syslog port):&lt;br /&gt;&lt;br /&gt;root@remy:/root&gt;/etc/init.d/syslog restart&lt;br /&gt;Shutting down kernel logger: [ OK ]&lt;br /&gt;Shutting down system logger: [ OK ]&lt;br /&gt;Starting system logger: [ OK ]&lt;br /&gt;Starting kernel logger: [ OK ]&lt;br /&gt;root@remy:/root&gt;netstat -an|grep 514&lt;br /&gt;udp 0 0 0.0.0.0:514 0.0.0.0:*&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;2) Now, configure your client:&lt;br /&gt;&lt;br /&gt;For simplicity, I added a line in the /etc/hosts file to add the name &#39;loghost&#39; to the other names I am using for my logging server. This is actually beneficial - because I can move my syslog server to another host - and I only have to modify the hosts file...&lt;br /&gt;&lt;br /&gt;Next, edit the /etc/syslog.conf file. I added 1 simple line to log all informational messages to the remote loghost:&lt;br /&gt;&lt;br /&gt;*.info @loghost&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Note: separate all columns with the tab character, not space.&lt;br /&gt;&lt;br /&gt;Finally restart syslog on the client with /etc/init.d/syslog restart.&lt;br /&gt;&lt;br /&gt;To test, you can use the command line logging facility called logger. On the client I type:&lt;br /&gt;&lt;br /&gt;root@booker:/etc&gt;logger foobar&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;And on the server I see:&lt;br /&gt;&lt;br /&gt;root@remy:/root&gt;tail -f /var/log/messages&lt;br /&gt;...&lt;br /&gt;Jun 28 21:17:29 booker bemo: foobar</content><link rel='replies' type='application/atom+xml' href='http://linuxscoop.blogspot.com/feeds/7075717519894261739/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/building-centralized-logging-server.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/7075717519894261739'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/7075717519894261739'/><link rel='alternate' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/building-centralized-logging-server.html' title='Building a Centralized Logging Server'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1019359938654970995.post-6667642089105453784</id><published>2011-01-22T11:28:00.001-08:00</published><updated>2011-01-22T11:28:57.669-08:00</updated><title type='text'>Setup DNS on Linux?</title><content type='html'>It has been long I was thinking of writing something about DNS(Domain Name Server).DNS is a database of the IP to Name and Name to IP conversion.I went through lots of tutorials related to DNS but couldnt satisfy myself unless and until I started writing commands and configuring files for the initial setup.After lot of tweaking and commandline I was able to setup a simple DNS server.&lt;br /&gt;&lt;br /&gt;Lets travel into the world of DNS.&lt;br /&gt;I have a RHEL 4 Machine ready with bind packages installed.The Minimal requirement are:&lt;br /&gt;&lt;br /&gt;[root@localhost ~]# rpm -qa bind*&lt;br /&gt;bind-libs-9.2.4-24.EL4&lt;br /&gt;bind-utils-9.2.4-24.EL4&lt;br /&gt;bind-9.2.4-24.EL4&lt;br /&gt;bind-chroot-9.2.4-24.EL4&lt;br /&gt;bind-devel-9.2.4-24.EL4&lt;br /&gt;bind-libs-9.2.4-24.EL4&lt;br /&gt;[root@localhost ~]#&lt;br /&gt;&lt;br /&gt;The IP Details of my Machine are:&lt;br /&gt;[root@localhost ~]# ifconfig&lt;br /&gt;eth0 Link encap:Ethernet HWaddr 00:16:17:C6:BE:47&lt;br /&gt;inet addr:10.14.77.33 Bcast:10.14.77.127 Mask:255.255.255.128&lt;br /&gt;inet6 addr: fe80::216:17ff:fec6:be47/64 Scope:Link&lt;br /&gt;UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1&lt;br /&gt;RX packets:36287 errors:0 dropped:0 overruns:0 frame:0&lt;br /&gt;TX packets:19141 errors:0 dropped:0 overruns:0 carrier:0&lt;br /&gt;collisions:0 txqueuelen:1000&lt;br /&gt;RX bytes:5408275 (5.1 MiB) TX bytes:2370680 (2.2 MiB)&lt;br /&gt;Interrupt:201&lt;br /&gt;&lt;br /&gt;lo Link encap:Local Loopback&lt;br /&gt;inet addr:127.0.0.1 Mask:255.0.0.0&lt;br /&gt;inet6 addr: ::1/128 Scope:Host&lt;br /&gt;UP LOOPBACK RUNNING MTU:16436 Metric:1&lt;br /&gt;RX packets:18714 errors:0 dropped:0 overruns:0 frame:0&lt;br /&gt;TX packets:18714 errors:0 dropped:0 overruns:0 carrier:0&lt;br /&gt;collisions:0 txqueuelen:0&lt;br /&gt;RX bytes:10174891 (9.7 MiB) TX bytes:10174891 (9.7 MiB)&lt;br /&gt;&lt;br /&gt;[root@localhost ~]#&lt;br /&gt;&lt;br /&gt;The Exact Steps I followed are mentioned Below:&lt;br /&gt;&lt;br /&gt;1. Open a file /etc/hosts and make it look like this:&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;[root@localhost ~]# cat /etc/hosts&lt;br /&gt;# Do not remove the following line, or various programs&lt;br /&gt;# that require network functionality will fail.&lt;br /&gt;127.0.0.1 localhost.localdomain localhost&lt;br /&gt;&lt;br /&gt;[root@localhost ~]#&lt;br /&gt;&lt;br /&gt;2.Edit the file /etc/resolv.conf:&lt;br /&gt;&lt;br /&gt;[root@localhost ~]# cat /etc/resolv.conf&lt;br /&gt;; generated by /sbin/dhclient-script&lt;br /&gt;&lt;br /&gt;search tuxbuddy.logica.com&lt;br /&gt;nameserver 10.14.77.33&lt;br /&gt;[root@localhost ~]#&lt;br /&gt;&lt;br /&gt;3. Run this Command:&lt;br /&gt;&lt;br /&gt;[root@localhost ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0&lt;br /&gt;DEVICE=eth0&lt;br /&gt;BOOTPROTO=dhcp&lt;br /&gt;HWADDR=00:16:17:C6:BE:47&lt;br /&gt;ONBOOT=yes&lt;br /&gt;TYPE=Ethernet&lt;br /&gt;PEERDNS=no&lt;br /&gt;[root@localhost ~]#&lt;br /&gt;&lt;br /&gt;4. Follow this step:&lt;br /&gt;&lt;br /&gt;[root@localhost etc]# pwd&lt;br /&gt;/var/named/chroot/etc&lt;br /&gt;[root@localhost etc]# vi named.conf&lt;br /&gt;&lt;br /&gt;//&lt;br /&gt;// named.conf for Red Hat caching-nameserver&lt;br /&gt;//&lt;br /&gt;&lt;br /&gt;options {&lt;br /&gt;directory &quot;/var/named&quot;;&lt;br /&gt;dump-file &quot;/var/named/data/cache_dump.db&quot;;&lt;br /&gt;statistics-file &quot;/var/named/data/named_stats.txt&quot;;&lt;br /&gt;/*&lt;br /&gt;* If there is a firewall between you and nameservers you want&lt;br /&gt;* to talk to, you might need to uncomment the query-source&lt;br /&gt;* directive below. Previous versions of BIND always asked&lt;br /&gt;* questions using port 53, but BIND 8.1 uses an unprivileged&lt;br /&gt;* port by default.&lt;br /&gt;*/&lt;br /&gt;// query-source address * port 53;&lt;br /&gt;};&lt;br /&gt;&lt;br /&gt;//&lt;br /&gt;// a caching only nameserver config&lt;br /&gt;//&lt;br /&gt;controls {&lt;br /&gt;inet 127.0.0.1 allow { localhost; } keys { rndckey; };&lt;br /&gt;};&lt;br /&gt;&lt;br /&gt;zone &quot;.&quot; IN {&lt;br /&gt;type hint;&lt;br /&gt;file &quot;named.ca&quot;;&lt;br /&gt;};&lt;br /&gt;&lt;br /&gt;zone &quot;tuxbuddy.logica.com&quot; IN {&lt;br /&gt;type master;&lt;br /&gt;file &quot;tuxbuddy.logica.com.zone&quot;;&lt;br /&gt;allow-update { none; };&lt;br /&gt;};&lt;br /&gt;&lt;br /&gt;zone &quot;33.77.14.10.in-addr.arpa&quot; IN {&lt;br /&gt;type master;&lt;br /&gt;file &quot;10.14.77.33.zone&quot;;&lt;br /&gt;allow-update { none; };&lt;br /&gt;};&lt;br /&gt;&lt;br /&gt;zone &quot;localhost&quot; IN {&lt;br /&gt;type master;&lt;br /&gt;file &quot;localhost.zone&quot;;&lt;br /&gt;allow-update { none; };&lt;br /&gt;};&lt;br /&gt;&lt;br /&gt;zone &quot;0.0.127.in-addr.arpa&quot; IN {&lt;br /&gt;type master;&lt;br /&gt;file &quot;named.local&quot;;&lt;br /&gt;allow-update { none; };&lt;br /&gt;};&lt;br /&gt;&lt;br /&gt;zone &quot;0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa&quot; IN {&lt;br /&gt;type master;&lt;br /&gt;file &quot;named.ip6.local&quot;;&lt;br /&gt;allow-update { none; };&lt;br /&gt;};&lt;br /&gt;&lt;br /&gt;zone &quot;255.in-addr.arpa&quot; IN {&lt;br /&gt;type master;&lt;br /&gt;file &quot;named.broadcast&quot;;&lt;br /&gt;allow-update { none; };&lt;br /&gt;};&lt;br /&gt;&lt;br /&gt;zone &quot;0.in-addr.arpa&quot; IN {&lt;br /&gt;type master;&lt;br /&gt;file &quot;named.zero&quot;;&lt;br /&gt;allow-update { none; };&lt;br /&gt;};&lt;br /&gt;&lt;br /&gt;include &quot;/etc/rndc.key&quot;;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Save the file.&lt;br /&gt;&lt;br /&gt;5.Edit the Database Files:&lt;br /&gt;&lt;br /&gt;[root@localhost named]# pwd&lt;br /&gt;/var/named/chroot/var/named&lt;br /&gt;[root@localhost named]#vi tuxbuddy.logica.com&lt;br /&gt;&lt;br /&gt;$TTL 86400&lt;br /&gt;@ IN SOA station1.tuxbuddy.logica.com. root.station1.tuxbuddy.logica.com. (&lt;br /&gt;2009091100; Serial&lt;br /&gt;28800 ; Refresh&lt;br /&gt;14400 ; Retry&lt;br /&gt;3600000 ;Expire&lt;br /&gt;0 ) ; Negative&lt;br /&gt;&lt;br /&gt;@ IN NS station1.tuxbuddy.logica.com.&lt;br /&gt;@ IN A 10.14.77.33&lt;br /&gt;&lt;br /&gt;station1.tuxbuddy.logica.com. IN A 10.14.77.33&lt;br /&gt;www IN A 10.14.77.33&lt;br /&gt;ftp IN A 10.14.77.33&lt;br /&gt;pop IN A 10.14.77.33&lt;br /&gt;&lt;br /&gt;www1 IN CNAME station1.tuxbuddy.logica.com.&lt;br /&gt;www2 IN CNAME station2.tuxbuddy.logica.com.&lt;br /&gt;www.station1.tuxbuddy.logica.com IN A 10.14.77.33&lt;br /&gt;Innovation2.groupinfra.com. IN A 10.14.16.215&lt;br /&gt;@ IN MX 10 station1.tuxbuddy.logica.com.&lt;br /&gt;station1 IN MX 10 station1.tuxbuddy.logica.com.&lt;br /&gt;~&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;[root@localhost named]#&lt;br /&gt;&lt;br /&gt;6. Edit this file too:&lt;br /&gt;&lt;br /&gt;[root@localhost named]# pwd&lt;br /&gt;/var/named/chroot/var/named&lt;br /&gt;[root@localhost named]#&lt;br /&gt;&lt;br /&gt;[root@localhost named]# cat 10.14.77.33.zone&lt;br /&gt;$TTL 86400&lt;br /&gt;@ IN SOA station1.tuxbuddy.logica.com. root.station1.tuxbuddy.logica.com. (&lt;br /&gt;4 10800 3600 604800 86400 )&lt;br /&gt;IN NS station1.tuxbuddy.logica.com.&lt;br /&gt;33.77.14.10.IN-ADDR.ARPA. IN PTR station1.tuxbuddy.logica.com.&lt;br /&gt;[root@localhost named]#&lt;br /&gt;&lt;br /&gt;JUST REMEMBER DONT MISS ANY . during the configuration.&lt;br /&gt;DNS IS VERY SENSITIVE TO SINGLE SIGN.&lt;br /&gt;&lt;br /&gt;Thats ALL !!!&lt;br /&gt;&lt;br /&gt;YOUR SIMPLE DNS SERVER IS READY.&lt;br /&gt;&lt;br /&gt;Testing the DNS SERVER&lt;br /&gt;&lt;br /&gt;[root@localhost named]# dig -x 10.14.77.33&lt;br /&gt;&lt;br /&gt;; &lt;&lt;&gt;&gt; DiG 9.2.4 &lt;&lt;&gt;&gt; -x 10.14.77.33&lt;br /&gt;;; global options: printcmd&lt;br /&gt;;; Got answer:&lt;br /&gt;;; -&gt;&gt;HEADER&lt;&lt;- opcode: QUERY, status: NOERROR, id: 48322 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1 ;; QUESTION SECTION: ;33.77.14.10.in-addr.arpa. IN PTR ;; ANSWER SECTION: 33.77.14.10.in-addr.arpa. 86400 IN PTR station1.tuxbuddy.logica.com. ;; AUTHORITY SECTION: 33.77.14.10.in-addr.arpa. 86400 IN NS station1.tuxbuddy.logica.com.&lt;br /&gt;&lt;br /&gt;;; ADDITIONAL SECTION:&lt;br /&gt;station1.tuxbuddy.logica.com. 86400 IN A 10.14.77.33&lt;br /&gt;&lt;br /&gt;;; Query time: 1 msec&lt;br /&gt;;; SERVER: 10.14.77.33#53(10.14.77.33)&lt;br /&gt;;; WHEN: Wed Oct 7 07:28:30 2009&lt;br /&gt;;; MSG SIZE rcvd: 114&lt;br /&gt;&lt;br /&gt;[root@localhost named]#&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Just See..Your IP is resolving to Hostname and vice versa.&lt;br /&gt;&lt;br /&gt;Other Way to see if things work or not !!&lt;br /&gt;&lt;br /&gt;[root@localhost named]# host 10.14.77.33&lt;br /&gt;33.77.14.10.in-addr.arpa domain name pointer station1.tuxbuddy.logica.com.&lt;br /&gt;[root@localhost named]#&lt;br /&gt;&lt;br /&gt;These too,&lt;br /&gt;[root@localhost named]# host www&lt;br /&gt;www.tuxbuddy.logica.com has address 10.14.77.33&lt;br /&gt;[root@localhost named]#</content><link rel='replies' type='application/atom+xml' href='http://linuxscoop.blogspot.com/feeds/6667642089105453784/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/setup-dns-on-linux.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/6667642089105453784'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/6667642089105453784'/><link rel='alternate' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/setup-dns-on-linux.html' title='Setup DNS on Linux?'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1019359938654970995.post-5889935000585524008</id><published>2011-01-22T11:27:00.001-08:00</published><updated>2011-01-22T11:27:48.571-08:00</updated><title type='text'>How can I view Apache server performance status?</title><content type='html'>Apache server performance can be monitored using the Apache module mod_status. Server status is presented in an HTML page that gives the current server statistics in an easily readable form. The page can be also made automatically refresh with a compatible browser. Another page gives a simple machine-readable list of the current server state.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;The details given are:&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;•The number of children serving requests.&lt;br /&gt;&lt;br /&gt;•The number of idle children.&lt;br /&gt;&lt;br /&gt;•The status of each child, the number of requests that child has performed and the total number of bytes served by the child (*)&lt;br /&gt;&lt;br /&gt;•A total number of accesses and byte count served (*).&lt;br /&gt;&lt;br /&gt;•The time the server was started/restarted and the time it has been running for&lt;br /&gt;&lt;br /&gt;•Averages giving the number of requests per second, the number of bytes served per second and the average number of bytes per request (*).&lt;br /&gt;&lt;br /&gt;•The current percentage CPU used by each child and in total by Apache (*).&lt;br /&gt;&lt;br /&gt;•The current hosts and requests being processed (*).&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Details marked &quot;(*)&quot; are only available with ExtendedStatus On.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Activating Status Support for Apache&lt;br /&gt;&lt;br /&gt;To activate status reports only for browsers from the mydomain.com domain add the following code to your httpd.conf configuration file:&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;SetHandler server-status&lt;br /&gt;Order Deny,Allow&lt;br /&gt;Deny from all&lt;br /&gt;Allow from .mydomain.com&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Note: The lines above may already exist in your default httpd.conf file. If this is the case, you can simply uncomment this section to use the existing configuration.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;The server statistics can now be accessed by using a Web browser. To access the page http://mydomain.com/server-status.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Try accessing and get the result likewise:&lt;br /&gt;&lt;br /&gt;Apache Server Status for 10.14.236.98&lt;br /&gt;Server Version: Apache/2.0.52 (Red Hat)&lt;br /&gt;Server Built: Aug 7 2007 05:01:09&lt;br /&gt;&lt;br /&gt;--------------------------------------------------------------------------------&lt;br /&gt;&lt;br /&gt;Current Time: Sunday, 11-Oct-2009 21:38:25 IST&lt;br /&gt;Restart Time: Sunday, 11-Oct-2009 21:38:19 IST&lt;br /&gt;Parent Server Generation: 0&lt;br /&gt;Server uptime: 5 seconds&lt;br /&gt;Total accesses: 0 - Total Traffic: 0 kB&lt;br /&gt;CPU Usage: u0 s0 cu0 cs0&lt;br /&gt;0 requests/sec - 0 B/second -&lt;br /&gt;1 requests currently being processed, 7 idle workers&lt;br /&gt;_W______........................................................&lt;br /&gt;................................................................&lt;br /&gt;................................................................&lt;br /&gt;................................................................&lt;br /&gt;&lt;br /&gt;Scoreboard Key:&lt;br /&gt;&quot;_&quot; Waiting for Connection, &quot;S&quot; Starting up, &quot;R&quot; Reading Request,&lt;br /&gt;&quot;W&quot; Sending Reply, &quot;K&quot; Keepalive (read), &quot;D&quot; DNS Lookup,&lt;br /&gt;&quot;C&quot; Closing connection, &quot;L&quot; Logging, &quot;G&quot; Gracefully finishing,&lt;br /&gt;&quot;I&quot; Idle cleanup of worker, &quot;.&quot; Open slot with no current process&lt;br /&gt;&lt;br /&gt;Srv PID Acc M CPU SS Req Conn Child Slot Client VHost Request&lt;br /&gt;1-0 25523 0/0/0 W 0.00 0 0 0.0 0.00 0.00 158.234.236.15 relay.groupultra.com GET /server-status HTTP/1.1&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;--------------------------------------------------------------------------------&lt;br /&gt;Srv Child Server number - generation&lt;br /&gt;PID OS process ID&lt;br /&gt;Acc Number of accesses this connection / this child / this slot&lt;br /&gt;M Mode of operation&lt;br /&gt;CPU CPU usage, number of seconds&lt;br /&gt;SS Seconds since beginning of most recent request&lt;br /&gt;Req Milliseconds required to process most recent request&lt;br /&gt;Conn Kilobytes transferred this connection&lt;br /&gt;Child Megabytes transferred this child&lt;br /&gt;Slot Total megabytes transferred this slot&lt;br /&gt;&lt;br /&gt;--------------------------------------------------------------------------------&lt;br /&gt;SSL/TLS Session Cache Status:&lt;br /&gt;cache type: SHMCB, shared memory: 512000 bytes, current sessions: 0&lt;br /&gt;sub-caches: 32, indexes per sub-cache: 133&lt;br /&gt;index usage: 0%, cache usage: 0%&lt;br /&gt;total sessions stored since starting: 0&lt;br /&gt;total sessions expired since starting: 0&lt;br /&gt;total (pre-expiry) sessions scrolled out of the cache: 0&lt;br /&gt;total retrieves since starting: 0 hit, 0 miss&lt;br /&gt;total removes since starting: 0 hit, 0 miss&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;--------------------------------------------------------------------------------&lt;br /&gt;&lt;br /&gt;Apache/2.0.52 (Red Hat) Server at 10.14.236.98 Port 80</content><link rel='replies' type='application/atom+xml' href='http://linuxscoop.blogspot.com/feeds/5889935000585524008/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/how-can-i-view-apache-server.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/5889935000585524008'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/5889935000585524008'/><link rel='alternate' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/how-can-i-view-apache-server.html' title='How can I view Apache server performance status?'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1019359938654970995.post-72556092558794403</id><published>2011-01-22T11:26:00.002-08:00</published><updated>2011-01-22T11:27:01.557-08:00</updated><title type='text'>How can I rotate my application logs periodically in Red Hat Enterprise Linux?</title><content type='html'>Red Hat Enterprise Linux has a daily cron job named logrotate which runs /usr/sbin/logrotate /etc/logrotate.conf every day. it is designed to ease administration of systems that generate large numbers of log files.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;This job will first import all the policy files in directory of /etc/logrotate.d/ and do as the config file ask to, For example, /etc/logrotate.dsyslog defines /var/log/messages to be rotated weekly.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Suppose there is a log file /var/log/app_log which needs to be rotated every day, this is the example config file to make that happen (/etc/logrotate.d/app_log):&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;[root@dhcp-0-130 ~]# cat /etc/logrotate.d/app_log&lt;br /&gt;/var/log/app_log {&lt;br /&gt;rotate 2&lt;br /&gt;daily&lt;br /&gt;}&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;rotate #&lt;br /&gt;&lt;br /&gt;means log files are rotated times before being removed.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;daily&lt;br /&gt;&lt;br /&gt;means log files are rotated every day.&lt;br /&gt;&lt;br /&gt;Hope you got a glimpse of power of LinuX.&lt;br /&gt;&lt;br /&gt;Happy Logging !!</content><link rel='replies' type='application/atom+xml' href='http://linuxscoop.blogspot.com/feeds/72556092558794403/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/how-can-i-rotate-my-application-logs.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/72556092558794403'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/72556092558794403'/><link rel='alternate' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/how-can-i-rotate-my-application-logs.html' title='How can I rotate my application logs periodically in Red Hat Enterprise Linux?'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1019359938654970995.post-1194604468455088477</id><published>2011-01-22T11:26:00.001-08:00</published><updated>2011-01-22T11:26:26.809-08:00</updated><title type='text'>How to configure Directory Indexing in Apache?</title><content type='html'>Quick Tips:&lt;br /&gt;&lt;br /&gt;Edit the /etc/httpd/conf/httpd.conf file :&lt;br /&gt;&lt;br /&gt;Just Look at the line starting:&lt;br /&gt;&lt;br /&gt;[Please note: Do add lesser than sign in front of directory]&lt;br /&gt;directory &quot;/var/www/html/pdfs&quot;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Options Indexes FollowSymLinks&lt;br /&gt;AllowOverride None&lt;br /&gt;Order allow,deny&lt;br /&gt;Allow from all&lt;br /&gt;&lt;br /&gt;/Directory&lt;br /&gt;&lt;br /&gt;Restart the Apache.&lt;br /&gt;Try browsing http://localhost/pdfs</content><link rel='replies' type='application/atom+xml' href='http://linuxscoop.blogspot.com/feeds/1194604468455088477/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/how-to-configure-directory-indexing-in.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/1194604468455088477'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/1194604468455088477'/><link rel='alternate' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/how-to-configure-directory-indexing-in.html' title='How to configure Directory Indexing in Apache?'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1019359938654970995.post-6785988855368177033</id><published>2011-01-22T11:24:00.000-08:00</published><updated>2011-01-22T11:25:30.841-08:00</updated><title type='text'>Setting up Nagios on RHEL 5.3</title><content type='html'>Last week I thought of setting up Nagios on my Linux Box.I installed a fresh piece of RHEL on my Virtualbox and everything went fine. I thought of putting this complete setup on my blog and here it is : &quot;A Complete Monitoring Tool for your Linux Box&quot;&lt;br /&gt;&lt;br /&gt;Here is my Machine Configuration:&lt;br /&gt;&lt;br /&gt;[root@irc ~]# cat /etc/redhat-release&lt;br /&gt;Red Hat Enterprise Linux Server release 5.3 (Tikanga)&lt;br /&gt;[root@irc ~]#&lt;br /&gt;&lt;br /&gt;[root@irc ~]# uname -arn&lt;br /&gt;Linux irc.chatserver.com 2.6.18-128.el5 #1 SMP Wed Dec 17 11:41:38 EST 2008 x86_64 x86_64 x86_64 GNU/Linux&lt;br /&gt;[root@irc ~]#&lt;br /&gt;&lt;br /&gt;1) Create Account Information&lt;br /&gt;&lt;br /&gt;Become the root user.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;su -l&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Create a new nagios user account and give it a password.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;/usr/sbin/useradd -m nagios&lt;br /&gt;&lt;br /&gt;passwd nagios&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Create a new nagcmd group for allowing external commands to be submitted through the web interface. Add both the nagios user and the apache user to the group.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;/usr/sbin/groupadd nagcmd&lt;br /&gt;&lt;br /&gt;/usr/sbin/usermod -a -G nagcmd nagios&lt;br /&gt;&lt;br /&gt;/usr/sbin/usermod -a -G nagcmd apache&lt;br /&gt;&lt;br /&gt;2) Download Nagios and the Plugins&lt;br /&gt;&lt;br /&gt;Create a directory for storing the downloads.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;mkdir ~/downloads&lt;br /&gt;&lt;br /&gt;cd ~/downloads&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Download the source code tarballs of both Nagios and the Nagios plugins (visit http://www.nagios.org/download/ for links to the latest versions). These directions were tested with Nagios 3.1.1 and Nagios Plugins 1.4.11.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;wget http://prdownloads.sourceforge.net/sourceforge/nagios/nagios-3.2.0.tar.gz&lt;br /&gt;&lt;br /&gt;wget http://prdownloads.sourceforge.net/sourceforge/nagiosplug/nagios-plugins-1.4.11.tar.gz&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;3) Compile and Install Nagios&lt;br /&gt;&lt;br /&gt;Extract the Nagios source code tarball.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;cd ~/downloads&lt;br /&gt;&lt;br /&gt;tar xzf nagios-3.2.0.tar.gz&lt;br /&gt;&lt;br /&gt;cd nagios-3.2.0&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Run the Nagios configure script, passing the name of the group you created earlier like so:&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;./configure --with-command-group=nagcmd&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Compile the Nagios source code.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;make all&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Install binaries, init script, sample config files and set permissions on the external command directory.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;make install&lt;br /&gt;&lt;br /&gt;make install-init&lt;br /&gt;&lt;br /&gt;make install-config&lt;br /&gt;&lt;br /&gt;make install-commandmode&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Don&#39;t start Nagios yet - there&#39;s still more that needs to be done...&lt;br /&gt;&lt;br /&gt;4) Customize Configuration&lt;br /&gt;&lt;br /&gt;Sample configuration files have now been installed in the /usr/local/nagios/etc directory. These sample files should work fine for getting started with Nagios. You&#39;ll need to make just one change before you proceed...&lt;br /&gt;&lt;br /&gt;Edit the /usr/local/nagios/etc/objects/contacts.cfg config file with your favorite editor and change the email address associated with the nagiosadmin contact definition to the address you&#39;d like to use for receiving alerts.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;vi /usr/local/nagios/etc/objects/contacts.cfg&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;5) Configure the Web Interface&lt;br /&gt;&lt;br /&gt;Install the Nagios web config file in the Apache conf.d directory.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;make install-webconf&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Create a nagiosadmin account for logging into the Nagios web interface. Remember the password you assign to this account - you&#39;ll need it later.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;htpasswd -c /usr/local/nagios/etc/htpasswd.users nagiosadmin&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Restart Apache to make the new settings take effect.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;service httpd restart&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Note: Consider implementing the ehanced CGI security measures described here to ensure that your web authentication credentials are not compromised.&lt;br /&gt;&lt;br /&gt;6) Compile and Install the Nagios Plugins&lt;br /&gt;&lt;br /&gt;Extract the Nagios plugins source code tarball.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;cd ~/downloads&lt;br /&gt;&lt;br /&gt;tar xzf nagios-plugins-1.4.11.tar.gz&lt;br /&gt;&lt;br /&gt;cd nagios-plugins-1.4.11&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Compile and install the plugins.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;./configure --with-nagios-user=nagios --with-nagios-group=nagios&lt;br /&gt;&lt;br /&gt;make&lt;br /&gt;&lt;br /&gt;make install&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;7) Start Nagios&lt;br /&gt;&lt;br /&gt;Add Nagios to the list of system services and have it automatically start when the system boots.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;chkconfig --add nagios&lt;br /&gt;&lt;br /&gt;chkconfig nagios on&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Verify the sample Nagios configuration files.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;If there are no errors, start Nagios.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;service nagios start&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;8) Modify SELinux Settings&lt;br /&gt;&lt;br /&gt;Fedora ships with SELinux (Security Enhanced Linux) installed and in Enforcing mode by default. This can result in &quot;Internal Server Error&quot; messages when you attempt to access the Nagios CGIs.&lt;br /&gt;&lt;br /&gt;See if SELinux is in Enforcing mode.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;getenforce&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Put SELinux into Permissive mode.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;setenforce 0&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;To make this change permanent, you&#39;ll have to modify the settings in /etc/selinux/config and reboot.&lt;br /&gt;&lt;br /&gt;Instead of disabling SELinux or setting it to permissive mode, you can use the following command to run the CGIs under SELinux enforcing/targeted mode:&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;chcon -R -t httpd_sys_content_t /usr/local/nagios/sbin/&lt;br /&gt;&lt;br /&gt;chcon -R -t httpd_sys_content_t /usr/local/nagios/share/&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;For information on running the Nagios CGIs under Enforcing mode with a targeted policy, visit the Nagios Support Portal or Nagios Community Wiki.&lt;br /&gt;&lt;br /&gt;9) Login to the Web Interface&lt;br /&gt;&lt;br /&gt;You should now be able to access the Nagios web interface at the URL below. You&#39;ll be prompted for the username (nagiosadmin) and password you specified earlier.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;http://localhost/nagios/&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Click on the &quot;Service Detail&quot; navbar link to see details of what&#39;s being monitored on your local machine. It will take a few minutes for Nagios to check all the services associated with your machine, as the checks are spread out over time.&lt;br /&gt;&lt;br /&gt;10) Other Modifications&lt;br /&gt;&lt;br /&gt;Make sure your machine&#39;s firewall rules are configured to allow access to the web server if you want to access the Nagios interface remotely.&lt;br /&gt;&lt;br /&gt;Configuring email notifications is out of the scope of this documentation. While Nagios is currently configured to send you email notifications, your system may not yet have a mail program properly installed or configured. Refer to your system documentation, search the web, or look to the Nagios Support Portal or Nagios Community Wiki for specific instructions on configuring your system to send email messages to external addresses. More information on notifications can be found here.&lt;br /&gt;&lt;br /&gt;11) You&#39;re Done&lt;br /&gt;&lt;br /&gt;Congratulations! You sucessfully installed Nagios. Your journey into monitoring is just beginning.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Example:&lt;br /&gt;&lt;br /&gt;Say, If You Nagios Server is 10.14.236.140. You need to monitor the Linux Machine with IP: 10.14.236.70. You need to follow up like this:&lt;br /&gt;&lt;br /&gt;[root@irc objects]# pwd&lt;br /&gt;/usr/local/nagios/etc/objects&lt;br /&gt;[root@irc objects]#&lt;br /&gt;[root@irc objects]# ls&lt;br /&gt;commands.cfg localhost.cfg printer.cfg switch.cfg timeperiods.cfg&lt;br /&gt;contacts.cfg localhost.cfg.orig remotehost.cfg templates.cfg windows.cfg&lt;br /&gt;[root@irc objects]#&lt;br /&gt;&lt;br /&gt;The File should looks like:&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;# HOST DEFINITION&lt;br /&gt;#&lt;br /&gt;###############################################################################&lt;br /&gt;###############################################################################&lt;br /&gt;&lt;br /&gt;# Define a host for the local machine&lt;br /&gt;&lt;br /&gt;define host{&lt;br /&gt;use linux-server ; Name of host template to use&lt;br /&gt;; This host definition will inherit all variab les that are defined&lt;br /&gt;; in (or inherited by) the linux-server host t emplate definition.&lt;br /&gt;host_name localhost&lt;br /&gt;alias localhost&lt;br /&gt;address 127.0.0.1&lt;br /&gt;}&lt;br /&gt;&lt;br /&gt;define host{&lt;br /&gt;use linux-server ; Name of host template to use&lt;br /&gt;; This host definition will inherit all variab les that are defined&lt;br /&gt;; in (or inherited by) the linux-server host t emplate definition.&lt;br /&gt;host_name ideath.logic.com&lt;br /&gt;alias ideath&lt;br /&gt;address 10.14.236.140&lt;br /&gt;}&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;###############################################################################&lt;br /&gt;###############################################################################&lt;br /&gt;#&lt;br /&gt;# HOST GROUP DEFINITION&lt;br /&gt;#&lt;br /&gt;###############################################################################&lt;br /&gt;###############################################################################&lt;br /&gt;&lt;br /&gt;# Define an optional hostgroup for Linux machines&lt;br /&gt;&lt;br /&gt;define hostgroup{&lt;br /&gt;hostgroup_name linux-server ; The name of the hostgroup&lt;br /&gt;alias Linux Servers ; Long name of the group&lt;br /&gt;members localhost ; Comma separated list of hosts that belong to this group&lt;br /&gt;}&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;###############################################################################&lt;br /&gt;###############################################################################&lt;br /&gt;#&lt;br /&gt;# SERVICE DEFINITIONS&lt;br /&gt;#&lt;br /&gt;###############################################################################&lt;br /&gt;###############################################################################&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;# Define a service to &quot;ping&quot; the local machine&lt;br /&gt;&lt;br /&gt;define service{&lt;br /&gt;use local-service ; Name of service template to use&lt;br /&gt;host_name localhost&lt;br /&gt;service_description PING&lt;br /&gt;check_command check_ping!100.0,20%!500.0,60%&lt;br /&gt;}&lt;br /&gt;&lt;br /&gt;define service{&lt;br /&gt;use local-service ; Name of service template to use&lt;br /&gt;host_name ideath.logica.com&lt;br /&gt;service_description PING&lt;br /&gt;check_command check_ping!100.0,20%!500.0,60%&lt;br /&gt;}&lt;br /&gt;&lt;br /&gt;# Define a service to check the disk space of the root partition&lt;br /&gt;# on the local machine. Warning if &lt; 20% free, critical if # &lt; 10% free space on partition. define service{ use local-service ; Name of service template to use host_name localhost service_description Root Partition check_command check_local_disk!20%!10%!/ } define service{ use local-service ; Name of service template to use host_name ideath.logic.com service_description Root Partition check_command check_local_disk!20%!10%!/ } # Define a service to check the number of currently logged in # users on the local machine. Warning if &gt; 20 users, critical&lt;br /&gt;# if &gt; 50 users.&lt;br /&gt;&lt;br /&gt;define service{&lt;br /&gt;use local-service ; Name of service template to use&lt;br /&gt;host_name localhost&lt;br /&gt;service_description Current Users&lt;br /&gt;check_command check_local_users!20!50&lt;br /&gt;}&lt;br /&gt;&lt;br /&gt;define service{&lt;br /&gt;use local-service ; Name of service template to use&lt;br /&gt;host_name ideath.logic.com&lt;br /&gt;service_description Current Users&lt;br /&gt;check_command check_local_users!20!50&lt;br /&gt;}&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;# Define a service to check the number of currently running procs&lt;br /&gt;# on the local machine. Warning if &gt; 250 processes, critical if&lt;br /&gt;# &gt; 400 users.&lt;br /&gt;&lt;br /&gt;define service{&lt;br /&gt;use local-service ; Name of service template to use&lt;br /&gt;host_name localhost&lt;br /&gt;service_description Total Processes&lt;br /&gt;check_command check_local_procs!250!400!RSZDT&lt;br /&gt;}&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;define service{&lt;br /&gt;use local-service ; Name of service template to use&lt;br /&gt;host_name ideath.logic.com&lt;br /&gt;service_description Total Processes&lt;br /&gt;check_command check_local_procs!250!400!RSZDT&lt;br /&gt;}&lt;br /&gt;# Define a service to check the load on the local machine.&lt;br /&gt;&lt;br /&gt;define service{&lt;br /&gt;use local-service ; Name of service template to use&lt;br /&gt;host_name localhost&lt;br /&gt;service_description Current Load&lt;br /&gt;check_command check_local_load!5.0,4.0,3.0!10.0,6.0,4.0&lt;br /&gt;}&lt;br /&gt;&lt;br /&gt;define service{&lt;br /&gt;use local-service ; Name of service template to use&lt;br /&gt;host_name ideath.logic.com&lt;br /&gt;service_description Current Load&lt;br /&gt;check_command check_local_load!5.0,4.0,3.0!10.0,6.0,4.0&lt;br /&gt;}&lt;br /&gt;&lt;br /&gt;# Define a service to check the swap usage the local machine.&lt;br /&gt;# Critical if less than 10% of swap is free, warning if less than 20% is free&lt;br /&gt;&lt;br /&gt;define service{&lt;br /&gt;use local-service ; Name of service template to use&lt;br /&gt;host_name localhost&lt;br /&gt;service_description Swap Usage&lt;br /&gt;check_command check_local_swap!20!10&lt;br /&gt;}&lt;br /&gt;&lt;br /&gt;define service{&lt;br /&gt;use local-service ; Name of service template to use&lt;br /&gt;host_name ideath.logic.com&lt;br /&gt;service_description Swap Usage&lt;br /&gt;check_command check_local_swap!20!10&lt;br /&gt;}&lt;br /&gt;&lt;br /&gt;# Define a service to check SSH on the local machine.&lt;br /&gt;# Disable notifications for this service by default, as not all users may have SSH enabled.&lt;br /&gt;&lt;br /&gt;define service{&lt;br /&gt;use local-service ; Name of service template to use&lt;br /&gt;host_name localhost&lt;br /&gt;service_description SSH&lt;br /&gt;check_command check_ssh&lt;br /&gt;notifications_enabled 0&lt;br /&gt;}&lt;br /&gt;&lt;br /&gt;define service{&lt;br /&gt;use local-service ; Name of service template to use&lt;br /&gt;host_name ideath.logic.com&lt;br /&gt;service_description SSH&lt;br /&gt;check_command check_ssh&lt;br /&gt;check_period 24x7&lt;br /&gt;notifications_enabled 0&lt;br /&gt;is_volatile 0&lt;br /&gt;max_check_attempts 4&lt;br /&gt;normal_check_interval 5&lt;br /&gt;retry_check_interval 1&lt;br /&gt;contact_groups admins&lt;br /&gt;notification_options w,c,u,r&lt;br /&gt;notification_interval 960&lt;br /&gt;notification_period 24x7&lt;br /&gt;check_command check_ssh&lt;br /&gt;}&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;# Define a service to check HTTP on the local machine.&lt;br /&gt;# Disable notifications for this service by default, as not all users may have HTTP enabled.&lt;br /&gt;&lt;br /&gt;define service{&lt;br /&gt;use local-service ; Name of service template to use&lt;br /&gt;host_name localhost&lt;br /&gt;service_description HTTP&lt;br /&gt;check_command check_http&lt;br /&gt;notifications_enabled 0&lt;br /&gt;}&lt;br /&gt;&lt;br /&gt;define service{&lt;br /&gt;use local-service ; Name of service template to use&lt;br /&gt;host_name ideath.logic.com&lt;br /&gt;service_description HTTP&lt;br /&gt;check_command check_http&lt;br /&gt;notifications_enabled 0&lt;br /&gt;is_volatile 0&lt;br /&gt;max_check_attempts 4&lt;br /&gt;normal_check_interval 5&lt;br /&gt;retry_check_interval 1&lt;br /&gt;contact_groups admins&lt;br /&gt;notification_options w,c,u,r&lt;br /&gt;notification_interval 960&lt;br /&gt;notification_period 24x7&lt;br /&gt;check_command check_http&lt;br /&gt;}&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Ideath.logic.com is the hostname of 10.14.236.70.&lt;br /&gt;Do make entry in /etc/hosts if it is unable to resolve the IP(or else check the DNS).</content><link rel='replies' type='application/atom+xml' href='http://linuxscoop.blogspot.com/feeds/6785988855368177033/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/setting-up-nagios-on-rhel-53.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/6785988855368177033'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/6785988855368177033'/><link rel='alternate' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/setting-up-nagios-on-rhel-53.html' title='Setting up Nagios on RHEL 5.3'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1019359938654970995.post-1246375280611334241</id><published>2011-01-22T11:23:00.000-08:00</published><updated>2011-01-22T11:24:12.504-08:00</updated><title type='text'>How do I rotate log files?</title><content type='html'>I had a hectic time playing with the logs yesterday. I have a VirtualBox setup on Dell Lappy and was exploring more on Logging this time.In one of the interview I was asked on &quot;Logging&quot; and thought to give it a little more exploration.Here is what I really get to know about the logrotate.&lt;br /&gt;&lt;br /&gt;Happy Reading !!&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;The rotation of log files can be done with the logrotate.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;logrotate is designed to ease administration of systems that generate large numbers of log files. It allows automatic rotation, compression, removal, and mailing of log files. Each log file may be handled daily, weekly, monthly, or when it grows too large.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;The /etc/logrotate.conf is the main configuration file for log rotation. This file is pretty self explanatory. Some important values to keep in mind:&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;# rotate log files weekly&lt;br /&gt;weekly&lt;br /&gt;&lt;br /&gt;# keep 4 weeks worth of backlogs&lt;br /&gt;rotate 4&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Normally, logrotate is run as a daily cron job. It will not modify a log multiple times in one day unless the criteria for a log is based on the logs size and logrotate is being run multiple times each day.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;For example, to change the log setting for CUPS, follow the steps below:&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Edit /etc/logrotate.d/cups file and add the following lines:&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;rotate&lt;br /&gt;# Log files are rotated times before being removed If count is 0, old versions are&lt;br /&gt;removed rather then rotated.&lt;br /&gt;size&lt;br /&gt;# Log files are rotated when they grow bigger then size bytes. If size is followed by M,&lt;br /&gt;the size if assumed to be in megabytes. If the k is used, the size is in kilobytes. So size&lt;br /&gt;100, size 100k, and size 100M are all valid.&lt;br /&gt;compress&lt;br /&gt;# Old versions of log files are compressed with gzip by default.&lt;br /&gt;&lt;br /&gt;The file should look similar to the following:&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;/var/log/cups/*_log {&lt;br /&gt;missingok&lt;br /&gt;notifempty&lt;br /&gt;size 100k # log files will be rotated when they grow bigger that 100k.&lt;br /&gt;rotate 5 # will keep the logs for 5 weeks.&lt;br /&gt;compress # log files will be compressed.&lt;br /&gt;sharedscripts&lt;br /&gt;postrotate&lt;br /&gt;/etc/init.d/cups condrestart &gt;/dev/null 2&gt;1 || true&lt;br /&gt;endscript&lt;br /&gt;}&lt;br /&gt;&lt;br /&gt;Save the file and exit.</content><link rel='replies' type='application/atom+xml' href='http://linuxscoop.blogspot.com/feeds/1246375280611334241/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/how-do-i-rotate-log-files.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/1246375280611334241'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/1246375280611334241'/><link rel='alternate' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/how-do-i-rotate-log-files.html' title='How do I rotate log files?'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1019359938654970995.post-3343831830702840070</id><published>2011-01-22T11:12:00.000-08:00</published><updated>2011-01-22T11:14:31.939-08:00</updated><title type='text'>How to setup RAID 1 on Ubuntu?</title><content type='html'>RAID 1 creates a mirror on the second drive. .You will need to create RAID aware partitions on your drives before you can create RAID and you will need to install mdadm on Ubuntu. For a tutorial on that CLICK HERE.&lt;br /&gt;&lt;br /&gt;You may have to create the RAID device first by indicating the RAID device with the block major and minor numbers. Be sure to increment the &quot;2&quot; number by one each time you create an additional RAID device.&lt;br /&gt;&lt;br /&gt;# mknod /dev/md1 b 9 2&lt;br /&gt;&lt;br /&gt;This will create the device if you have already used /dev/md0.&lt;br /&gt;&lt;span style=&quot;font-weight:bold;&quot;&gt;&lt;br /&gt;Create RAID 1&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;# mdadm --create /dev/md1 --level=1 --raid-devices=2 /dev/sdb7 /dev/sdb8&lt;br /&gt;&lt;br /&gt;--create&lt;br /&gt;This will create a RAID array. The device that you will use for the first RAID array is /dev/md1.&lt;br /&gt;&lt;br /&gt;--level=1&lt;br /&gt;The level option determines what RAID level you will use for the RAID.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;--raid-devices=2 /dev/sdb7 /dev/sdb8&lt;br /&gt;Note: for illustration or practice this shows two partitions on the same drive. This is NOT what you want to do, partitions must be on separate drives. However, this will provide you with a practice scenario. You must list the number of devices in the RAID array and you must list the devices that you have partitioned with fdisk. The example shows two RAID partitions.&lt;br /&gt;mdadm: array /dev/md0 started.&lt;br /&gt;&lt;br /&gt;&lt;span style=&quot;font-weight:bold;&quot;&gt;&lt;br /&gt;Verify the Create of the RAID&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;# cat /proc/mdstat&lt;br /&gt;&lt;br /&gt;Personalities : [raid0] [raid1]&lt;br /&gt;&lt;br /&gt;md2 : active raid1 sdb8[1] sdb7[0]&lt;br /&gt;&lt;br /&gt;497856 blocks [2/2] [UU]&lt;br /&gt;&lt;br /&gt;[======&gt;..............] resync = 34.4% (172672/497856) finish=0.2min speed=21584K/sec&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;md0 : active raid0 sdb6[1] sdb5[0]&lt;br /&gt;&lt;br /&gt;995712 blocks 64k chunks&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;unused devices:&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;# tail /var/log/messages&lt;br /&gt;&lt;br /&gt;You can also verify that RAID is being built in /var/log/messages.&lt;br /&gt;&lt;br /&gt;May 19 09:21:45 ub1 kernel: [ 5320.433192] md: raid1 personality registered for level 1&lt;br /&gt;&lt;br /&gt;May 19 09:21:45 ub1 kernel: [ 5320.433620] md2: WARNING: sdb7 appears to be on the same physical disk as sdb8.&lt;br /&gt;&lt;br /&gt;May 19 09:21:45 ub1 kernel: [ 5320.433628] True protection against single-disk failure might be compromised.&lt;br /&gt;&lt;br /&gt;May 19 09:21:45 ub1 kernel: [ 5320.433772] raid1: raid set md2 active with 2 out of 2 mirrors&lt;br /&gt;&lt;br /&gt;May 19 09:21:45 ub1 kernel: [ 5320.433913] md: resync of RAID array md2&lt;br /&gt;&lt;br /&gt;May 19 09:21:45 ub1 kernel: [ 5320.433926] md: minimum _guaranteed_ speed: 1000 KB/sec/disk.&lt;br /&gt;&lt;br /&gt;May 19 09:21:45 ub1 kernel: [ 5320.433934] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for resync.&lt;br /&gt;&lt;br /&gt;May 19 09:21:45 ub1 kernel: [ 5320.433954] md: using 128k window, over a total of 497856 blocks.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Create the File System ext 3.&lt;br /&gt;You have to place a file system on your RAID device. The journaling system ext3 is placed on the device in this example.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;# mke2fs -j /dev/md1&lt;br /&gt;&lt;br /&gt;mke2fs 1.40.8 (13-Mar-2008)&lt;br /&gt;&lt;br /&gt;Filesystem label=&lt;br /&gt;&lt;br /&gt;OS type: Linux&lt;br /&gt;&lt;br /&gt;Block size=1024 (log=0)&lt;br /&gt;&lt;br /&gt;Fragment size=1024 (log=0)&lt;br /&gt;&lt;br /&gt;124928 inodes, 497856 blocks&lt;br /&gt;&lt;br /&gt;24892 blocks (5.00%) reserved for the super user&lt;br /&gt;&lt;br /&gt;First data block=1&lt;br /&gt;&lt;br /&gt;Maximum filesystem blocks=67633152&lt;br /&gt;&lt;br /&gt;61 block groups&lt;br /&gt;&lt;br /&gt;8192 blocks per group, 8192 fragments per group&lt;br /&gt;&lt;br /&gt;2048 inodes per group&lt;br /&gt;&lt;br /&gt;Superblock backups stored on blocks:&lt;br /&gt;&lt;br /&gt;8193, 24577, 40961, 57345, 73729, 204801, 221185, 401409&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Writing inode tables: done&lt;br /&gt;&lt;br /&gt;Creating journal (8192 blocks): done&lt;br /&gt;&lt;br /&gt;Writing superblocks and filesystem accounting information: done&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;This filesystem will be automatically checked every 35 mounts or&lt;br /&gt;&lt;br /&gt;180 days, whichever comes first. Use tune2fs -c or -i to override.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style=&quot;font-weight:bold;&quot;&gt;Mount the RAID on the /raid Partition&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;In order to use the RAID array you will need to mount it on the file system. For testing purposes you can create a mount point and test. To make a permanent mount point you will need to edit /etc/fstab.&lt;br /&gt;&lt;br /&gt;# mount /dev/md1 /raid&lt;br /&gt;&lt;br /&gt;# df&lt;br /&gt;The df command will verify that it has mounted.&lt;br /&gt;&lt;br /&gt;Filesystem 1K-blocks Used Available Use% Mounted on&lt;br /&gt;&lt;br /&gt;/dev/sda2 5809368 2699256 2817328 49% /&lt;br /&gt;&lt;br /&gt;varrun 1037732 104 1037628 1% /var/run&lt;br /&gt;&lt;br /&gt;varlock 1037732 0 1037732 0% /var/lock&lt;br /&gt;&lt;br /&gt;udev 1037732 80 1037652 1% /dev&lt;br /&gt;&lt;br /&gt;devshm 1037732 12 1037720 1% /dev/shm&lt;br /&gt;&lt;br /&gt;/dev/sda1 474440 49252 400691 11% /boot&lt;br /&gt;&lt;br /&gt;/dev/sda4 474367664 1738024 448722912 1% /home&lt;br /&gt;&lt;br /&gt;/dev/md1 482090 10544 446654 3% /raid&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;You should be able to create files on the new partition. If this works then you may edit the /etc/fstab and add a line that looks like this:&lt;br /&gt;&lt;br /&gt;/dev/md1 /raid defaults 0 2&lt;br /&gt;&lt;br /&gt;Be sure to test and be prepared to enter single user mode to fix any problems with the new RAID device.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style=&quot;font-weight:bold;&quot;&gt;Create a Failed RAID Disk&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;In order to test your RAID 1 you can fail a disk, remove it and reinstall it. This is an important feature to practice.&lt;br /&gt;&lt;br /&gt;# mdadm /dev/md1 -f /dev/sdb8&lt;br /&gt;This will deliberately make the /dev/sdb8 faulty.&lt;br /&gt;&lt;br /&gt;mdadm: set /dev/sdb8 faulty in /dev/md1&lt;br /&gt;&lt;br /&gt;root@ub1:/etc/network# cat /proc/mdstat&lt;br /&gt;&lt;br /&gt;Personalities : [raid0] [raid1]&lt;br /&gt;&lt;br /&gt;md2 : active raid1 sdb8[2](F) sdb7[0]&lt;br /&gt;&lt;br /&gt;497856 blocks [2/1] [U_]&lt;br /&gt;&lt;br /&gt;md0 : active raid0 sdb6[1] sdb5[0]&lt;br /&gt;&lt;br /&gt;995712 blocks 64k chunks&lt;br /&gt;&lt;br /&gt;unused devices:&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Hot Remove the Failed Disk&lt;br /&gt;You can remove the faulty disk from the RAID array.&lt;br /&gt;&lt;br /&gt;# mdadm /dev/md1 -r /dev/sdb8&lt;br /&gt;&lt;br /&gt;mdadm: hot removed /dev/sdb8&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Verify the Process&lt;br /&gt;&lt;br /&gt;You should be able to see the process as it is working.&lt;br /&gt;&lt;br /&gt;# cat /proc/mdstat&lt;br /&gt;&lt;br /&gt;Personalities : [raid0] [raid1]&lt;br /&gt;&lt;br /&gt;md2 : active raid1 sdb7[0]&lt;br /&gt;&lt;br /&gt;497856 blocks [2/1] [U_]&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;md0 : active raid0 sdb6[1] sdb5[0]&lt;br /&gt;&lt;br /&gt;995712 blocks 64k chunks&lt;br /&gt;&lt;br /&gt;unused devices:&lt;br /&gt;&lt;br /&gt;Add a Replacement Drive HOT&lt;br /&gt;&lt;br /&gt;This will allow you to add a device into the array to replace the bad one.&lt;br /&gt;# mdadm /dev/md1 -a /dev/sdb8&lt;br /&gt;&lt;br /&gt;mdadm: re-added /dev/sdb8&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Verify the Process.&lt;br /&gt;&lt;br /&gt;# cat /proc/mdstat&lt;br /&gt;&lt;br /&gt;Personalities : [raid0] [raid1]&lt;br /&gt;&lt;br /&gt;md2 : active raid1 sdb8[2] sdb7[0]&lt;br /&gt;&lt;br /&gt;497856 blocks [2/1] [U_]&lt;br /&gt;&lt;br /&gt;[=====&gt;...............] recovery = 26.8% (134464/497856) finish=0.2min speed=26892K/sec&lt;br /&gt;&lt;br /&gt;md0 : active raid0 sdb6[1] sdb5[0]&lt;br /&gt;&lt;br /&gt;995712 blocks 64k chunks&lt;br /&gt;&lt;br /&gt;unused devices:&lt;br /&gt;Posted by LinuxFreaker at 10:48</content><link rel='replies' type='application/atom+xml' href='http://linuxscoop.blogspot.com/feeds/3343831830702840070/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/how-to-setup-raid-1-on-ubuntu.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/3343831830702840070'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/3343831830702840070'/><link rel='alternate' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/how-to-setup-raid-1-on-ubuntu.html' title='How to setup RAID 1 on Ubuntu?'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1019359938654970995.post-7181929800649955982</id><published>2011-01-22T11:09:00.000-08:00</published><updated>2011-01-22T11:11:32.099-08:00</updated><title type='text'>How to setup RAID 0 on Ubuntu Linux?</title><content type='html'>RAID 0 will create striping to increase read/write speeds as the data can be read and written on separate disks at the same time. This level of RAID is what you want to use if you need to increase the speed of disk access.You will need to create RAID aware partitions on your drives before you can create RAID and you will need to install mdadm on Ubuntu. &lt;br /&gt;&lt;br /&gt;These commands must be done as root or you must add the sudo command in front of each command.&lt;br /&gt;&lt;br /&gt;# mdadm --create /dev/md0 --level=0 --raid-devices=2 /dev/sdb5 /dev/sdb6&lt;br /&gt;&lt;br /&gt;--create&lt;br /&gt;This will create a RAID array. The device that you will use for the first RAID array is /dev/md0.&lt;br /&gt;&lt;br /&gt;--level=0&lt;br /&gt;The level option determines what RAID level you will use for the RAID.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;--raid-devices=2 /dev/sdb5 /dev/sdb6&lt;br /&gt;Note: for illustration or practice this shows two partitions on the same drive. This is NOT what you want to do, partitions must be on separate drives. However, this will provide you with a practice scenario. You must list the number of devices in the RAID array and you must list the devices that you have partitioned with fdisk. The example shows two RAID partitions.&lt;br /&gt;mdadm: array /dev/md0 started.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Check the development of the RAID.&lt;br /&gt;&lt;br /&gt;# cat /proc/mdstat&lt;br /&gt;&lt;br /&gt;Personalities : [raid0]&lt;br /&gt;&lt;br /&gt;md0 : active raid0 sdb6[1] sdb5[0]&lt;br /&gt;&lt;br /&gt;995712 blocks 64k chunks&lt;br /&gt;unused devices:&lt;br /&gt;&lt;br /&gt;# tail /var/log/messages&lt;br /&gt;You can also verify that RAID is being built in /var/log/messages.&lt;br /&gt;&lt;br /&gt;May 19 09:08:51 ub1 kernel: [ 4548.276806] raid0: looking at sdb5&lt;br /&gt;&lt;br /&gt;May 19 09:08:51 ub1 kernel: [ 4548.276809] raid0: comparing sdb5(497856) with sdb6(497856)&lt;br /&gt;&lt;br /&gt;May 19 09:08:51 ub1 kernel: [ 4548.276813] raid0: EQUAL&lt;br /&gt;&lt;br /&gt;May 19 09:08:51 ub1 kernel: [ 4548.276815] raid0: FINAL 1 zones&lt;br /&gt;&lt;br /&gt;May 19 09:08:51 ub1 kernel: [ 4548.276822] raid0: done.&lt;br /&gt;&lt;br /&gt;May 19 09:08:51 ub1 kernel: [ 4548.276826] raid0 : md_size is 995712 blocks.&lt;br /&gt;&lt;br /&gt;May 19 09:08:51 ub1 kernel: [ 4548.276829] raid0 : conf-&gt;hash_spacing is 995712 blocks.&lt;br /&gt;&lt;br /&gt;May 19 09:08:51 ub1 kernel: [ 4548.276831] raid0 : nb_zone is 1.&lt;br /&gt;&lt;br /&gt;May 19 09:08:51 ub1 kernel: [ 4548.276834] raid0 : Allocating 4 bytes for hash.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Create the ext 3 File System&lt;br /&gt;You have to place a file system on your RAID device. The journaling system ext3 is placed on the device in this example.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;# mke2fs -j /dev/md0&lt;br /&gt;&lt;br /&gt;mke2fs 1.40.8 (13-Mar-2008)&lt;br /&gt;&lt;br /&gt;Filesystem label=&lt;br /&gt;&lt;br /&gt;OS type: Linux&lt;br /&gt;&lt;br /&gt;Block size=4096 (log=2)&lt;br /&gt;&lt;br /&gt;Fragment size=4096 (log=2)&lt;br /&gt;&lt;br /&gt;62464 inodes, 248928 blocks&lt;br /&gt;&lt;br /&gt;12446 blocks (5.00%) reserved for the super user&lt;br /&gt;&lt;br /&gt;First data block=0&lt;br /&gt;&lt;br /&gt;Maximum filesystem blocks=255852544&lt;br /&gt;&lt;br /&gt;8 block groups&lt;br /&gt;&lt;br /&gt;32768 blocks per group, 32768 fragments per group&lt;br /&gt;&lt;br /&gt;7808 inodes per group&lt;br /&gt;&lt;br /&gt;Superblock backups stored on blocks:&lt;br /&gt;&lt;br /&gt;32768, 98304, 163840, 229376&lt;br /&gt;&lt;br /&gt;Writing inode tables: done&lt;br /&gt;&lt;br /&gt;Creating journal (4096 blocks): done&lt;br /&gt;&lt;br /&gt;Writing superblocks and filesystem accounting information: done&lt;br /&gt;&lt;br /&gt;This filesystem will be automatically checked every 39 mounts or&lt;br /&gt;&lt;br /&gt;180 days, whichever comes first. Use tune2fs -c or -i to override.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Create a Place to Mount the RAID on the File System&lt;br /&gt;&lt;br /&gt;In order to use the RAID array you will need to mount it on the file system. For testing purposes you can create a mount point and test. To make a permanent mount point you will need to edit /etc/fstab.&lt;br /&gt;&lt;br /&gt;# mkdir /raid&lt;br /&gt;&lt;br /&gt;Mount the RAID Array&lt;br /&gt;&lt;br /&gt;# mount /dev/md0 /raid&lt;br /&gt;&lt;br /&gt;You should be able to create files on the new partition. If this works then you may edit the /etc/fstab and add a line that looks like this:&lt;br /&gt;&lt;br /&gt;/dev/md0 /raid defaults 0 2&lt;br /&gt;&lt;br /&gt;Be sure to test and be prepared to enter single user mode to fix any problems with the new RAID device. &lt;br /&gt;&lt;br /&gt;Hope you find this article helpful.</content><link rel='replies' type='application/atom+xml' href='http://linuxscoop.blogspot.com/feeds/7181929800649955982/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/how-to-setup-raid-0-on-ubuntu-linux.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/7181929800649955982'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/7181929800649955982'/><link rel='alternate' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/how-to-setup-raid-0-on-ubuntu-linux.html' title='How to setup RAID 0 on Ubuntu Linux?'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1019359938654970995.post-4882177865619200558</id><published>2011-01-22T10:58:00.000-08:00</published><updated>2011-01-22T11:05:16.340-08:00</updated><title type='text'>Integrating Active Directory Server to Linux</title><content type='html'>Linux and Windows System Administrators generally undergoes tough time working in integrated environment. Sometimes Linux freaks are required to integrate Linux environment with Windows environment while other time Windows administrators do face problems working in Linux command line.&lt;br /&gt;&lt;br /&gt;One of my colleague working as Linux System Administrator was asked to connect ADS to Linux box.Since he has 3 years of experience working only as Linux system admin he did faced issues configuring the same in Windows. He shared the experience with me and I collected the steps.Hope it would be helpful for whoever wanna tweak with it.&lt;br /&gt;Here it goes..&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Prerequisite:&lt;br /&gt;&lt;br /&gt;Following Samba client RPM’s must be pre-installed on the server:&lt;br /&gt;&lt;br /&gt;samba-client-3.0.33-3.7.el5&lt;br /&gt;samba-common-3.0.33-3.7.el5&lt;br /&gt;&lt;br /&gt;01)Configuring Linux networking:&lt;br /&gt;&lt;br /&gt;a)Make sure that your host file has proper entries for your server [if it is static IP ].&lt;br /&gt;&lt;br /&gt;b)Configure DNS client properly. Entries for /etc/resolv.conf file:&lt;br /&gt;&lt;br /&gt;search sap.com&lt;br /&gt;nameserver 10.210.1.252&lt;br /&gt;nameserver 10.219.1.252&lt;br /&gt;&lt;br /&gt;02)Synchronize the time using NTP.&lt;br /&gt;&lt;br /&gt;a)Remove all public server IP’s/Names from /etc/ntp.conf and replace with the Company DNS server IP.&lt;br /&gt;&lt;br /&gt;server 10.222.1.252&lt;br /&gt;&lt;br /&gt;b)Synchronize the time with spaient time server.&lt;br /&gt;&lt;br /&gt;#ntpdate -u 10.222.1.252&lt;br /&gt;&lt;br /&gt;c)Start the NTP daemon&lt;br /&gt;&lt;br /&gt;# service ntpd restart&lt;br /&gt;&lt;br /&gt;d)Set the NTP service to start at boot time.&lt;br /&gt;&lt;br /&gt;#chkconfig --level 234 ntpd on&lt;br /&gt;&lt;br /&gt;03)Configuring PAM and NSS&lt;br /&gt;&lt;br /&gt;a)Run the system-config-authentication in GUI or setup [for authentication configuration] command in CLI.&lt;br /&gt;&lt;br /&gt;# system-config-authentication&lt;br /&gt;&lt;br /&gt;Check the Winbind option on both the User Information tab (which configures the nss.conf file) and the Authentication tab (which modifies system-auth file).&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Click the Configure Winbind button and enter the following entries:&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;b)Open the /etc/pam.d/system-auth file, then scroll down toward the bottom and insert a highlighted line before the last line. This will create a home directory for a user if doesn’t exists.&lt;br /&gt;&lt;br /&gt;session [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid&lt;br /&gt;&lt;br /&gt;session required pam_mkhomedir.so skel=/etc/skel/ umask=0022&lt;br /&gt;&lt;br /&gt;session required pam_unix.so&lt;br /&gt;&lt;br /&gt;04)Open the /etc/samba/smb.conf and add/edit the highlighted entries in the global section of this file.&lt;br /&gt;&lt;br /&gt;[global]&lt;br /&gt;#--authconfig--start-line--&lt;br /&gt;&lt;br /&gt;# Generated by authconfig on 2010/02/13 11:48:48&lt;br /&gt;&lt;br /&gt;workgroup = sap&lt;br /&gt;password server = dellads2&lt;br /&gt;realm = SAP.COM&lt;br /&gt;security = ads&lt;br /&gt;idmap uid = 16777216-33554431&lt;br /&gt;idmap gid = 16777216-33554431&lt;br /&gt;idmap backend = rid&lt;br /&gt;template shell = /bin/bash&lt;br /&gt;template homedir = /home/%U&lt;br /&gt;winbind use default domain = true&lt;br /&gt;winbind offline logon = false&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;05)Domain Join and Logging in:&lt;br /&gt;a)Add that machine into a Sapient domain&lt;br /&gt;&lt;br /&gt;#net ads join -U&lt;br /&gt;&lt;br /&gt;Note: Required NT-ID of a Company IT member who has privileges to add machine into a domain.&lt;br /&gt;&lt;br /&gt;b)Start the winbind service and set it up for startup at boot time.&lt;br /&gt;&lt;br /&gt;# service winbind restart&lt;br /&gt;# chkconfig --level 234 winbind on&lt;br /&gt;&lt;br /&gt;Try logging into the server using your NTID.&lt;br /&gt;&lt;br /&gt;Thats Done.</content><link rel='replies' type='application/atom+xml' href='http://linuxscoop.blogspot.com/feeds/4882177865619200558/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/integrating-active-directory-server-to.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/4882177865619200558'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/4882177865619200558'/><link rel='alternate' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/integrating-active-directory-server-to.html' title='Integrating Active Directory Server to Linux'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1019359938654970995.post-2224616064082557858</id><published>2011-01-15T07:03:00.000-08:00</published><updated>2011-01-16T06:30:13.204-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Cron"/><title type='text'>How to install Cron on CentOS Linux?</title><content type='html'>I have a CentOS Box which was without cron package installed.When I tried running crond service it says &quot;Unrecognized service&quot;. I thought of installing through:&lt;br /&gt;
&lt;br /&gt;
#yum install cron&lt;br /&gt;
&lt;br /&gt;
But that din&#39;t help. So I explored and came up with the solution as below:&lt;br /&gt;
&lt;br /&gt;
[root@localhost graphs]# service crond restart&lt;br /&gt;
crond: unrecognized service&lt;br /&gt;
&lt;br /&gt;
[root@localhostgraphs]# rpm -qa | grep cron&lt;br /&gt;
crontabs-1.10-8&lt;br /&gt;
[root@localhostgraphs]# rpmquery --whatprovides $(which crontab)&lt;br /&gt;
file /usr/bin/crontab is not owned by any package&lt;br /&gt;
[root@localhost tl_graphs]# rpmquery --whatprovides $(which crontab)&lt;br /&gt;
file /usr/bin/crontab is not owned by any package&lt;br /&gt;
[root@localhost graphs]# yum install vixie-cron&lt;br /&gt;
Setting up Install Process&lt;br /&gt;
Parsing package install arguments&lt;br /&gt;
Resolving Dependencies&lt;br /&gt;
--&gt; Running transaction check&lt;br /&gt;
---&gt; Package vixie-cron.i386 4:4.1-76.el5 set to be updated&lt;br /&gt;
--&gt; Finished Dependency Resolution&lt;br /&gt;
&lt;br /&gt;
Dependencies Resolved&lt;br /&gt;
&lt;br /&gt;
=============================================================================&lt;br /&gt;
Package Arch Version Repository Size&lt;br /&gt;
=============================================================================&lt;br /&gt;
Installing:&lt;br /&gt;
vixie-cron i386 4:4.1-76.el5 base 78 k&lt;br /&gt;
&lt;br /&gt;
Transaction Summary&lt;br /&gt;
=============================================================================&lt;br /&gt;
Install 1 Package(s)&lt;br /&gt;
Update 0 Package(s)&lt;br /&gt;
Remove 0 Package(s)&lt;br /&gt;
&lt;br /&gt;
Total download size: 78 k&lt;br /&gt;
Is this ok [y/N]: y&lt;br /&gt;
Downloading Packages:&lt;br /&gt;
(1/1): vixie-cron-4.1-76. 100% |=========================| 78 kB 00:00&lt;br /&gt;
Running rpm_check_debug&lt;br /&gt;
Running Transaction Test&lt;br /&gt;
Finished Transaction Test&lt;br /&gt;
Transaction Test Succeeded&lt;br /&gt;
Running Transaction&lt;br /&gt;
Installing: vixie-cron ######################### [1/1]&lt;br /&gt;
&lt;br /&gt;
Installed: vixie-cron.i386 4:4.1-76.el5&lt;br /&gt;
Complete!&lt;br /&gt;
[root@localhost graphs]# service crond restart&lt;br /&gt;
Stopping crond: cannot stop crond: crond is not running. [FAILED]&lt;br /&gt;
Starting crond: [ OK ]&lt;br /&gt;
[root@localhost graphs]#&lt;br /&gt;
&lt;br /&gt;
So I have crond service running on my CentOS.&lt;br /&gt;
Happy CronDing !!!</content><link rel='replies' type='application/atom+xml' href='http://linuxscoop.blogspot.com/feeds/2224616064082557858/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/how-to-install-cron-on-centos-linux.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/2224616064082557858'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/2224616064082557858'/><link rel='alternate' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/how-to-install-cron-on-centos-linux.html' title='How to install Cron on CentOS Linux?'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1019359938654970995.post-42157570281705123</id><published>2011-01-15T06:55:00.000-08:00</published><updated>2011-01-16T03:52:07.753-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Kernel"/><category scheme="http://www.blogger.com/atom/ns#" term="Linux"/><category scheme="http://www.blogger.com/atom/ns#" term="PAE"/><category scheme="http://www.blogger.com/atom/ns#" term="RHEL5"/><title type='text'>How to install Linux PAE enabled kernel?</title><content type='html'>If you are testing 32-bit RHEL5, please make sure that we use PAE kernel instead of the default kernel that is installed.With the default kernel, 32-bit RHEL5 will not recognize more than 4GB of guest memory even though you configure it on the VM..&lt;br /&gt;
So please verify the following before you so the testing....&lt;br /&gt;
&lt;br /&gt;
a) Check the kernel that is installed when you install the distribution&lt;br /&gt;
(RHEL5 32-bit &amp; 64-bit)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[root@localhost ~]# uname -r&lt;br /&gt;
2.6.18-8.el5 &lt;br /&gt;
&lt;br /&gt;
The above output indicates that the kernel that is installed is neither PAE / huge mem kernel.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You can find the list of installed kernel using:&lt;br /&gt;
&lt;br /&gt;
# rpm -qa | grep -i kernel&lt;br /&gt;
&lt;br /&gt;
kernel-2.6.18-8.el5&lt;br /&gt;
kernel-headers-2.6.18-8.el5&lt;br /&gt;
kernel-devel-2.6.18-8.el5&lt;br /&gt;
&lt;br /&gt;
For the guest to use more than 4GB, we need to install the PAE kernel (You will get that from RHEL5 CD1..)&lt;br /&gt;
&lt;br /&gt;
rhel-5-server-i386-disc1.iso&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
c) Mount the cdrom&lt;br /&gt;
&lt;br /&gt;
mount /dev/cdrom /mnt&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
d) You will see something similar to this:&lt;br /&gt;
&lt;br /&gt;
# ls /mnt/Server/ | grep -i 2.6.18-8&lt;br /&gt;
kernel-2.6.18-8.el5.i686.rpm&lt;br /&gt;
kernel-devel-2.6.18-8.el5.i686.rpm&lt;br /&gt;
kernel-doc-2.6.18-8.el5.noarch.rpm&lt;br /&gt;
kernel-headers-2.6.18-8.el5.i386.rpm&lt;br /&gt;
kernel-PAE-2.6.18-8.el5.i686.rpm&lt;br /&gt;
kernel-PAE-devel-2.6.18-8.el5.i686.rpm&lt;br /&gt;
kernel-xen-2.6.18-8.el5.i686.rpm&lt;br /&gt;
kernel-xen-devel-2.6.18-8.el5.i686.rpm&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
At a shell prompt, change to the directory that contains the kernel RPM packages. Use -i argument with the rpm command to keep the old kernel.&lt;br /&gt;
&lt;br /&gt;
Caution: Do not use the -U option, since it overwrites the currently installed kernel, which creates boot loader problems. &lt;br /&gt;
&lt;br /&gt;
For example:&lt;br /&gt;
&lt;br /&gt;
[root@localhost]# rpm -ivh kernel-PAE-2.6.18-8.el5.i686.rpm&lt;br /&gt;
&lt;br /&gt;
warning: kernel-PAE-2.6.18-8.el5.i686.rpm: Header V3 DSA signature: NOKEY,&lt;br /&gt;
key ID 37017186&lt;br /&gt;
Preparing... ########################################### [100%]&lt;br /&gt;
1:kernel-PAE ########################################### [100%]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Verify the initial RAM disk image.&lt;br /&gt;
&lt;br /&gt;
To verify that an initial RAM disk already exists, use the command ls -l /boot to make sure the initrd-.img file was created (the version should match the version of the kernel just installed).&lt;br /&gt;
&lt;br /&gt;
# ls -l /boot/ | grep img&lt;br /&gt;
&lt;br /&gt;
-rw------- 1 root root 2318314 Jun 2 06:41 initrd-2.6.18-8.el5.img&lt;br /&gt;
-rw------- 1 root root 2319154 Jun 4 08:18 initrd-2.6.18-8.el5PAE.img &lt;br /&gt;
&lt;br /&gt;
This shows the new image that is created...&lt;br /&gt;
&lt;br /&gt;
Verifying the boot loader..&lt;br /&gt;
&lt;br /&gt;
[root@localhost]# cat /boot/grub/grub.conf | grep PAE&lt;br /&gt;
title Red Hat Enterprise Linux Server (2.6.18-8.el5PAE)&lt;br /&gt;
kernel /vmlinuz-2.6.18-8.el5PAE ro root=/dev/VolGroup00/LogVol00 rhgb&lt;br /&gt;
quiet&lt;br /&gt;
initrd /initrd-2.6.18-8.el5PAE.img&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Done. Restart the guest and at the grub menu press the key &quot;e&quot; and select the PAE kernel.&lt;br /&gt;
&lt;br /&gt;
[root@localhost ~]# uname -r&lt;br /&gt;
2.6.18-8.el5PAE&lt;br /&gt;
&lt;br /&gt;
[root@localhost ~]# cat /proc/meminfo | grep -i memtotal&lt;br /&gt;
&lt;br /&gt;
MemTotal: 4934652 kB (I set only 5GB and it should go upto 64GB&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you want to always boot with PAE kernel, please do the changes in /etc/grub.conf.&lt;br /&gt;
&lt;br /&gt;
Edit /etc/grub.conf to make default=0 (on my server new kernel is 0th kernel).&lt;br /&gt;
&lt;br /&gt;
This is how it looks like:&lt;br /&gt;
&lt;br /&gt;
default=0&lt;br /&gt;
timeout=5&lt;br /&gt;
splashimage=(hd0,0)/grub/splash.xpm.gz&lt;br /&gt;
hiddenmenu&lt;br /&gt;
title Red Hat Enterprise Linux Server (2.6.18-8.el5PAE)&lt;br /&gt;
root (hd0,0)&lt;br /&gt;
kernel /vmlinuz-2.6.18-8.el5PAE ro root=/dev/VolGroup00/LogVol00 rhgb quiet&lt;br /&gt;
initrd /initrd-2.6.18-8.el5PAE.img&lt;br /&gt;
&lt;br /&gt;
title Red Hat Enterprise Linux Server (2.6.18-8.el5)&lt;br /&gt;
root (hd0,0)&lt;br /&gt;
kernel /vmlinuz-2.6.18-8.el5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet&lt;br /&gt;
initrd /initrd-2.6.18-8.el5.img</content><link rel='replies' type='application/atom+xml' href='http://linuxscoop.blogspot.com/feeds/42157570281705123/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/how-to-install-linux-pae-enabled-kernel.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/42157570281705123'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/42157570281705123'/><link rel='alternate' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/how-to-install-linux-pae-enabled-kernel.html' title='How to install Linux PAE enabled kernel?'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1019359938654970995.post-8878579421001006837</id><published>2011-01-08T00:54:00.000-08:00</published><updated>2011-01-16T03:52:53.774-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Git"/><category scheme="http://www.blogger.com/atom/ns#" term="Version Control System"/><title type='text'>Understanding Git - Part- II</title><content type='html'>&lt;b&gt;What is Git?&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
Git is a distributed revision control system with an emphasis on speed. Git was initially designed and developed by Linus Torvalds for Linux kernel development.&lt;br /&gt;
&lt;br /&gt;
Every Git working directory is a full-fledged repository with complete history and full revision tracking capabilities, not dependent on network access or a central server.&lt;br /&gt;
&lt;br /&gt;
Git’s current software maintenance is overseen by Junio Hamano. Distributed under the terms of version 2 of the GNU General Public License, git is free software.&lt;br /&gt;
&lt;br /&gt;
Git is a free &amp; open source, distributed version control system  designed to handle everything from small to very large projects with speed and efficiency.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;How Git Works?&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;div class=&quot;separator&quot; style=&quot;clear: both; text-align: center;&quot;&gt;&lt;a href=&quot;http://3.bp.blogspot.com/_AcbMFlT19gk/TSglnH0kPAI/AAAAAAAAAjI/u9FzkN9tLu4/s1600/git-1.jpg&quot; imageanchor=&quot;1&quot; style=&quot;clear:left; float:left;margin-right:1em; margin-bottom:1em&quot;&gt;&lt;img border=&quot;0&quot; height=&quot;214&quot; width=&quot;320&quot; src=&quot;http://3.bp.blogspot.com/_AcbMFlT19gk/TSglnH0kPAI/AAAAAAAAAjI/u9FzkN9tLu4/s320/git-1.jpg&quot; /&gt;&lt;/a&gt;&lt;/div&gt;&lt;br /&gt;
Git is a decentralized version control system which means that there is no any kind of centralized repository (as SVN) rather we have distributed repository where each user has their own repository and they have freedom to create branches and experiment rather than creating branches at the central repo (as in SVN).&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;How to install Git on Windows and Linux?&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
Windows&lt;br /&gt;
&lt;br /&gt;
1. Download Cygwin.&lt;br /&gt;
2. Put setup.exe in a folder of its own in your documents.&lt;br /&gt;
3. Launch setup.exe.&lt;br /&gt;
4. While installing Cygwin, pick these packages:&lt;br /&gt;
* git from the DEVEL category&lt;br /&gt;
* nano (if you’re wimpy) or vim (if you know it), both in the EDITORS category&lt;br /&gt;
&lt;br /&gt;
You’ll now have a shortcut to launch Cygwin, which brings up something like the Linux terminal.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Linux&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
Install the git package using your preferred method (package manager or from source).&lt;br /&gt;
&lt;br /&gt;
yum install git-core&lt;br /&gt;
&lt;br /&gt;
Introduce Yourself to Git&lt;br /&gt;
&lt;br /&gt;
Fire up your Cygwin/Linux terminal, and type:&lt;br /&gt;
&lt;br /&gt;
git config --global user.name &quot;Joey Joejoe&quot;&lt;br /&gt;
git config --global user.email &quot;joey@joejoe.com&quot;&lt;br /&gt;
&lt;br /&gt;
You only need to do this once.&lt;br /&gt;
&lt;br /&gt;
Start Your Project&lt;br /&gt;
&lt;br /&gt;
Start your project using the Sphere editor, or from a ZIP file, or just by making the directory and adding files yourself.&lt;br /&gt;
&lt;br /&gt;
Now cd to your project directory:&lt;br /&gt;
&lt;br /&gt;
cd myproject/&lt;br /&gt;
&lt;br /&gt;
Tell git to start giving a damn about your project:&lt;br /&gt;
&lt;br /&gt;
git init&lt;br /&gt;
&lt;br /&gt;
… and your files in it:&lt;br /&gt;
&lt;br /&gt;
git add .&lt;br /&gt;
&lt;br /&gt;
Wrap it up:&lt;br /&gt;
&lt;br /&gt;
git commit&lt;br /&gt;
&lt;br /&gt;
Now type in a “commit message”: a reminder to yourself of what you’ve just done, like:&lt;br /&gt;
&lt;br /&gt;
Initial commit.&lt;br /&gt;
&lt;br /&gt;
Save it and quit (type Ctrl+o Ctrl+x if you’re in nano, :x if you’re in vim) and you’re done!&lt;br /&gt;
&lt;br /&gt;
When dealing with git, it’s best to work in small bits. Rule of thumb: if you can’t summarise it in a sentence, you’ve gone too long without committing.&lt;br /&gt;
&lt;br /&gt;
This section is your typical work cycle:&lt;br /&gt;
&lt;br /&gt;
1. Work on your project.&lt;br /&gt;
2. Check which files you’ve changed:&lt;br /&gt;
&lt;br /&gt;
git status&lt;br /&gt;
&lt;br /&gt;
3. Check what the actual changes were:&lt;br /&gt;
&lt;br /&gt;
git diff&lt;br /&gt;
&lt;br /&gt;
4. Add any files/folders mentioned in step 2 (or new ones):&lt;br /&gt;
&lt;br /&gt;
git add file1 newfile2 newfolder3&lt;br /&gt;
&lt;br /&gt;
5. Commit your work:&lt;br /&gt;
&lt;br /&gt;
git commit&lt;br /&gt;
&lt;br /&gt;
6. Enter and save your commit message. If you want to back out, just quit the editor.&lt;br /&gt;
&lt;br /&gt;
Repeat as much as you like. Just remember to always end with a commit.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;What you did till now?&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
To see what you’ve done so far, type:&lt;br /&gt;
&lt;br /&gt;
git log&lt;br /&gt;
&lt;br /&gt;
To just see the last few commits you’ve made:&lt;br /&gt;
&lt;br /&gt;
git log -n3&lt;br /&gt;
&lt;br /&gt;
Replace 3 with whatever you feel like.&lt;br /&gt;
&lt;br /&gt;
For a complete overview, type:&lt;br /&gt;
&lt;br /&gt;
git log --stat --summary&lt;br /&gt;
&lt;br /&gt;
Browse at your leisure.&lt;br /&gt;
&lt;br /&gt;
What changes you made?&lt;br /&gt;
&lt;br /&gt;
To view changes you haven’t committed yet:&lt;br /&gt;
&lt;br /&gt;
git diff&lt;br /&gt;
&lt;br /&gt;
If you want changes between versions of your project, first you’ll need to know the commit ID for the changes:&lt;br /&gt;
&lt;br /&gt;
git log --pretty=oneline&lt;br /&gt;
&lt;br /&gt;
6c93a1960072710c6677682a7816ba9e48b7528f Remove persist.clearScriptCache() function.&lt;br /&gt;
c6e7f6e685edbb414c676df259aab989b617b018 Make git ignore logs directory.&lt;br /&gt;
8fefbce334d30466e3bb8f24d11202a8f535301c Initial commit.&lt;br /&gt;
&lt;br /&gt;
The 40 characters at the front of each line is the commit ID. You’ll also see them when you git commit. You can use it to show differences between commits.&lt;br /&gt;
&lt;br /&gt;
To view the changes between the 1st and 2nd commits, type:&lt;br /&gt;
&lt;br /&gt;
git diff 8fef..c6e7&lt;br /&gt;
&lt;br /&gt;
Note how you didn’t have to type the whole thing, just the first few unique characters are enough.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;To view the last changes you made:&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
git diff HEAD^..HEAD&lt;br /&gt;
&lt;br /&gt;
Troubleshoot?&lt;br /&gt;
&lt;br /&gt;
Haven’t committed yet, but don’t want to save the changes? You can throw them away:&lt;br /&gt;
&lt;br /&gt;
git reset --hard&lt;br /&gt;
&lt;br /&gt;
You can also do it for individual files, but it’s a bit different:&lt;br /&gt;
&lt;br /&gt;
git checkout myfile.txt&lt;br /&gt;
&lt;br /&gt;
Messed up the commit message? This will let you re-enter it:&lt;br /&gt;
&lt;br /&gt;
git commit --amend&lt;br /&gt;
&lt;br /&gt;
Forgot something in your last commit? That’s easy to fix.&lt;br /&gt;
&lt;br /&gt;
git reset --soft HEAD^&lt;br /&gt;
&lt;br /&gt;
Add that stuff you forgot:&lt;br /&gt;
&lt;br /&gt;
git add forgot.txt these.txt&lt;br /&gt;
&lt;br /&gt;
Then write over the last commit:&lt;br /&gt;
&lt;br /&gt;
git commit&lt;br /&gt;
&lt;br /&gt;
Don’t make a habit of overwriting/changing history if it’s a public repo you’re working with, though.&lt;br /&gt;
&lt;br /&gt;
Hope you liked this post relevant and useful.&lt;br /&gt;
&lt;br /&gt;
In the next article we shall dig deep into Workflow which makes Git flexible tool to use both the decentralized and centralized version control system.&lt;br /&gt;
&lt;br /&gt;
Please go through this presentation before we proceed with the different workflow.&lt;br /&gt;
&lt;br /&gt;
&lt;a href=&quot;http://www.scribd.com/doc/33285834/Git-Vs-SVN&quot;&gt;Git Vs SVN&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;a href=&quot;http://www.youtube.com/watch?feature=player_embedded&amp;v=iwYKX9H8UcI&quot;&gt;Introduction to Git&lt;/a&gt;</content><link rel='replies' type='application/atom+xml' href='http://linuxscoop.blogspot.com/feeds/8878579421001006837/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/understanding-git-part-ii.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/8878579421001006837'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/8878579421001006837'/><link rel='alternate' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/understanding-git-part-ii.html' title='Understanding Git - Part- II'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://3.bp.blogspot.com/_AcbMFlT19gk/TSglnH0kPAI/AAAAAAAAAjI/u9FzkN9tLu4/s72-c/git-1.jpg" height="72" width="72"/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1019359938654970995.post-1768596924141151970</id><published>2011-01-06T11:30:00.000-08:00</published><updated>2011-01-06T11:31:00.262-08:00</updated><title type='text'>Setting up a Simple Samba Share - Part II</title><content type='html'>In the previous article we saw the practical implication of setting up a samba share.In this article we will explore more about the Samba with practical approach.&lt;br /&gt;
&lt;br /&gt;
Aim:&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Connnecting to Samba Server through Own Client Software on the same machine&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
Implementation:&lt;br /&gt;
&lt;br /&gt;
[root@rhel samba]# smbclient //localhost/ -U jen&lt;br /&gt;
Password:&lt;br /&gt;
Domain=[rhel] OS=[Unix] Server=[Samba 3.0.25b-0.4E.6]&lt;br /&gt;
tree connect failed: NT_STATUS_BAD_NETWORK_NAME&lt;br /&gt;
[root@rhel samba]# smbclient //localhost/jen -U jen&lt;br /&gt;
Password:&lt;br /&gt;
Domain=[rhel] OS=[Unix] Server=[Samba 3.0.25b-0.4E.6]&lt;br /&gt;
smb: \&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You will see lots of commands here:&lt;br /&gt;
&lt;br /&gt;
smb: \&gt; ?&lt;br /&gt;
? altname archive blocksize cancel&lt;br /&gt;
case_sensitive cd chmod chown close&lt;br /&gt;
del dir du exit get&lt;br /&gt;
getfacl hardlink help history lcd&lt;br /&gt;
link lock lowercase ls mask&lt;br /&gt;
md mget mkdir more mput&lt;br /&gt;
newer open posix posix_open posix_mkdir&lt;br /&gt;
posix_rmdir posix_unlink print prompt put&lt;br /&gt;
pwd q queue quit rd&lt;br /&gt;
recurse reget rename reput rm&lt;br /&gt;
rmdir showacls setmode stat symlink&lt;br /&gt;
tar tarmode translate unlock volume&lt;br /&gt;
vuid wdel logon listconnect showconnect&lt;br /&gt;
!&lt;br /&gt;
&lt;br /&gt;
smb: \&gt;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
Lets put a file called text1 from the share to a directory /tmp&lt;br /&gt;
Here it goes:&lt;br /&gt;
&lt;br /&gt;
[root@rhel samba]# cd /home/jen/&lt;br /&gt;
[root@rhel jen]# ls&lt;br /&gt;
[root@rhel jen]# touch text &lt;&lt;----- Lets Create a file called text1
[root@rhel jen]# vi text
[root@rhel jen]# smbclient //localhost/jen -U jen
Password:
Domain=[rhel] OS=[Unix] Server=[Samba 3.0.25b-0.4E.6]
smb: \&gt; ls&lt;br /&gt;
. D 0 Mon Aug 3 17:16:20 2009&lt;br /&gt;
.. D 0 Mon Aug 3 17:02:24 2009&lt;br /&gt;
.bash_logout H 24 Mon Aug 3 17:02:24 2009&lt;br /&gt;
.kde DH 0 Mon Aug 3 17:02:24 2009&lt;br /&gt;
.gtkrc H 120 Mon Aug 3 17:02:24 2009&lt;br /&gt;
.bash_profile H 191 Mon Aug 3 17:02:24 2009&lt;br /&gt;
text 6 Mon Aug 3 17:16:20 2009 &lt;&lt;--- Here is a file
.bashrc H 124 Mon Aug 3 17:02:24 2009

50521 blocks of size 262144. 27714 blocks available
smb: \&gt;&lt;br /&gt;
&lt;br /&gt;
Remember currently we are now in /tmp directory:&lt;br /&gt;
&lt;br /&gt;
[root@rhel jen]# cd /tmp&lt;br /&gt;
[root@rhel tmp]# smbclient //localhost/jen -U jen&lt;br /&gt;
Password:&lt;br /&gt;
Domain=[rhel] OS=[Unix] Server=[Samba 3.0.25b-0.4E.6]&lt;br /&gt;
smb: \&gt; ls&lt;br /&gt;
. D 0 Mon Aug 3 17:16:20 2009&lt;br /&gt;
.. D 0 Mon Aug 3 17:02:24 2009&lt;br /&gt;
.bash_logout H 24 Mon Aug 3 17:02:24 2009&lt;br /&gt;
.kde DH 0 Mon Aug 3 17:02:24 2009&lt;br /&gt;
.gtkrc H 120 Mon Aug 3 17:02:24 2009&lt;br /&gt;
.bash_profile H 191 Mon Aug 3 17:02:24 2009&lt;br /&gt;
text 6 Mon Aug 3 17:16:20 2009&lt;br /&gt;
.bashrc H 124 Mon Aug 3 17:02:24 2009&lt;br /&gt;
&lt;br /&gt;
50521 blocks of size 262144. 27714 blocks available&lt;br /&gt;
smb: \&gt; get text&lt;br /&gt;
getting file \text of size 6 as text (60000.0 kb/s) (average inf kb/s)&lt;br /&gt;
smb: \&gt;&lt;br /&gt;
&lt;br /&gt;
Now, When I browse /tmp directory i can see:&lt;br /&gt;
&lt;br /&gt;
[root@rhel tmp]# ls&lt;br /&gt;
mapping-root text&lt;br /&gt;
[root@rhel tmp]#&lt;br /&gt;
&lt;br /&gt;
Aim:&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Seting up a Samba Server which avails documents and printer to only the system regular users and not to anyone outside.&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
Implementation:&lt;br /&gt;
&lt;br /&gt;
1. Share Point ==&gt; /export&lt;br /&gt;
2. All files owned by user called Ajeet Raina&lt;br /&gt;
&lt;br /&gt;
Lets create a user :&lt;br /&gt;
&lt;br /&gt;
[root@rhel tmp]# useradd -c &quot;Ajeet Raina&quot; -m -g users -p Oracle9ias ajeetr&lt;br /&gt;
[root@rhel tmp]# mkdir /export&lt;br /&gt;
[root@rhel tmp]# chmod u+rw,g+rw,o+rw /export&lt;br /&gt;
[root@rhel tmp]# chown ajeetr.users /export&lt;br /&gt;
[root@rhel tmp]#&lt;br /&gt;
&lt;br /&gt;
Copy the files that should be shared to the /export directory.</content><link rel='replies' type='application/atom+xml' href='http://linuxscoop.blogspot.com/feeds/1768596924141151970/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/setting-up-simple-samba-share-part-ii.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/1768596924141151970'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/1768596924141151970'/><link rel='alternate' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/setting-up-simple-samba-share-part-ii.html' title='Setting up a Simple Samba Share - Part II'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1019359938654970995.post-6089343858519190454</id><published>2011-01-06T11:20:00.000-08:00</published><updated>2011-01-16T03:53:22.031-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Samba"/><category scheme="http://www.blogger.com/atom/ns#" term="System Admin"/><title type='text'>Setting up a Simple Samba Share - Part I</title><content type='html'>The best definition I found for Samba goes this way &quot;Samba is an important component to seamlessly integrate Linux/Unix Servers and Desktops into Active Directory environments using the winbind daemon&quot;.In simple words, Samba is the standard Windows interoperability suite of programs for Linux and Unix.Since long  back in 1992, Samba has provided secure, stable and fast file and print services for all clients using the SMB/CIFS protocol, such as all versions of DOS and Windows, OS/2, Linux and many others. &lt;br /&gt;
&lt;br /&gt;
Today we are going to setup a simple samba share.&lt;br /&gt;
&lt;br /&gt;
Setting Up a Simple Samba Share which can be accessed by anyone who has account on the Machine.&lt;br /&gt;
&lt;br /&gt;
Backup the smb.conf file&lt;br /&gt;
------------------------------------------&lt;br /&gt;
&lt;br /&gt;
Locating the Correct Samba configuration File:&lt;br /&gt;
&lt;br /&gt;
[root@rhel samba]# smbd -b | grep smb.conf&lt;br /&gt;
CONFIGFILE: /etc/samba/smb.conf&lt;br /&gt;
[root@rhel samba]#&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[root@rhel ~]# cd /etc/samba/&lt;br /&gt;
[root@rhel samba]# cp smb.conf smb.conf.orig&lt;br /&gt;
[root@rhel samba]# &gt; smb.conf&lt;br /&gt;
[root@rhel samba]# vi smb.conf&lt;br /&gt;
&lt;br /&gt;
Add a simple Homes Share in smb.conf&lt;br /&gt;
------------------------------------------------------&lt;br /&gt;
&lt;br /&gt;
[root@rhel samba]# cat smb.conf&lt;br /&gt;
&lt;br /&gt;
[global]&lt;br /&gt;
workgroup = MIDEARTH&lt;br /&gt;
[homes]&lt;br /&gt;
guest ok = no&lt;br /&gt;
read only = no&lt;br /&gt;
&lt;br /&gt;
[root@rhel samba]#&lt;br /&gt;
&lt;br /&gt;
[root@rhel samba]# service smb restart&lt;br /&gt;
Shutting down SMB services: [FAILED]&lt;br /&gt;
Shutting down NMB services: [FAILED]&lt;br /&gt;
Starting SMB services: [ OK ]&lt;br /&gt;
Starting NMB services: [ OK ]&lt;br /&gt;
[root@rhel samba]#&lt;br /&gt;
&lt;br /&gt;
Add a user called Jen&lt;br /&gt;
-----------------------------&lt;br /&gt;
&lt;br /&gt;
[root@rhel samba]# useradd jen&lt;br /&gt;
[root@rhel samba]# passwd jen&lt;br /&gt;
Changing password for user jen.&lt;br /&gt;
New UNIX password:&lt;br /&gt;
BAD PASSWORD: it is WAY too short&lt;br /&gt;
Retype new UNIX password:&lt;br /&gt;
passwd: all authentication tokens updated successfully.&lt;br /&gt;
&lt;br /&gt;
Provide him with smb credentials(this is different from normal user/pass credentials)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[root@rhel samba]# smbpasswd -a jen&lt;br /&gt;
New SMB password:&lt;br /&gt;
Retype new SMB password:&lt;br /&gt;
Added user jen.&lt;br /&gt;
[root@rhel samba]#&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Go to Start &gt; Run &gt; \\MachineIP&lt;br /&gt;
Login in through user/pass&lt;br /&gt;
Successfull !!!&lt;br /&gt;
&lt;br /&gt;
You can see home directory [homes] and jen own home directory&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Testing Your Samba Share&lt;br /&gt;
-------------------------&lt;br /&gt;
&lt;br /&gt;
[root@rhel samba]# testparm /etc/samba/smb.conf&lt;br /&gt;
Load smb config files from /etc/samba/smb.conf&lt;br /&gt;
Processing section &quot;[homes]&quot;&lt;br /&gt;
Loaded services file OK.&lt;br /&gt;
Server role: ROLE_STANDALONE&lt;br /&gt;
Press enter to see a dump of your service definitions&lt;br /&gt;
&lt;br /&gt;
[global]&lt;br /&gt;
workgroup = MIDEARTH&lt;br /&gt;
&lt;br /&gt;
[homes]&lt;br /&gt;
read only = No&lt;br /&gt;
[root@rhel samba]#&lt;br /&gt;
&lt;br /&gt;
List Shares Available on the Server&lt;br /&gt;
-----------------------------------------------&lt;br /&gt;
&lt;br /&gt;
[root@rhel samba]# smbclient -L rhel -U jen&lt;br /&gt;
Password:&lt;br /&gt;
Domain=[rhel] OS=[Unix] Server=[Samba 3.0.25b-0.4E.6]&lt;br /&gt;
&lt;br /&gt;
Sharename Type Comment&lt;br /&gt;
--------- ---- -------&lt;br /&gt;
homes Disk&lt;br /&gt;
IPC$ IPC IPC Service (Samba 3.0.25b-0.4E.6)&lt;br /&gt;
jen Disk Home directory of jen&lt;br /&gt;
Domain=[rhel] OS=[Unix] Server=[Samba 3.0.25b-0.4E.6]&lt;br /&gt;
&lt;br /&gt;
Server Comment&lt;br /&gt;
--------- -------&lt;br /&gt;
&lt;br /&gt;
Workgroup Master&lt;br /&gt;
--------- -------&lt;br /&gt;
MIDEARTH BL07DL380G5&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Done. Your first samba share is Ready !!!</content><link rel='replies' type='application/atom+xml' href='http://linuxscoop.blogspot.com/feeds/6089343858519190454/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/setting-up-simple-samba-share-part-i.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/6089343858519190454'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/6089343858519190454'/><link rel='alternate' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/setting-up-simple-samba-share-part-i.html' title='Setting up a Simple Samba Share - Part I'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1019359938654970995.post-7379746734119755930</id><published>2011-01-06T10:50:00.000-08:00</published><updated>2011-01-16T03:54:05.163-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Kernel"/><category scheme="http://www.blogger.com/atom/ns#" term="Linux"/><title type='text'>Linux Kernel 2.6.37 Announced</title><content type='html'>The Linux kernel 2.6.37 is finally announced by Linus Torvald on 4 January 2011.The announcement can be found &lt;a href=&quot;https://lkml.org/lkml/2011/1/4/266&quot;&gt;here&lt;/a&gt;.The kernel is now stable and can be downloaded from &lt;a href=&quot;http://kernel.org.&quot;&gt;http://kernel.org.&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
The kernel includes several SMP scalability improvements for Ext4 and XFS, removal of the BKL (Big Kernel Lock) from the core code,a network device based in the Ceph cluster filesystem, new Btrfs capabilities  (namely the Btrfs space cache option), more efficient static probes, perf support to probe modules and listing of accesible local and global variables, PPP over IPv4 support, improvements and new drivers.&lt;br /&gt;
&lt;br /&gt;
The Linux 2.6.37 kernel is already been shipped with an upcoming Ubuntu 11.04 Alpha 2 release yesterday.The detail information of advancement and new features which came with this kernel release can be explored through &lt;a href=&quot;http://kernelnewbies.org/Linux_2_6_37&quot;&gt;http://kernelnewbies.org/Linux_2_6_37&lt;/a&gt;</content><link rel='replies' type='application/atom+xml' href='http://linuxscoop.blogspot.com/feeds/7379746734119755930/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/linux-kernel-2637-announced.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/7379746734119755930'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/7379746734119755930'/><link rel='alternate' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/linux-kernel-2637-announced.html' title='Linux Kernel 2.6.37 Announced'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1019359938654970995.post-2304800592853651239</id><published>2011-01-03T11:22:00.000-08:00</published><updated>2011-01-16T03:54:26.165-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Linux"/><category scheme="http://www.blogger.com/atom/ns#" term="Swap"/><title type='text'>Need to add extra swap space? Read this</title><content type='html'>&quot;Can Linux be installed without swap space?&quot;. This question might sound confusing for those who listen it for the first time and never tried out. But the reality is &quot;Yes&quot;. But if you did this, you should be ready to cope up with your Linux box next time you put extra load on your box.It will crash someday.&lt;br /&gt;
Its always recommended to provide extra space for swap partition.Swap is only used when you have maximum load.&lt;br /&gt;
&lt;br /&gt;
This article discuss how to increase the swap space through adding swap file on Linux machine.&lt;br /&gt;
&lt;br /&gt;
Lets proceed with the requisite steps to add swap file as shown below:&lt;br /&gt;
&lt;br /&gt;
Lets use dd command to create swapfile. Then you need to use mkswap command to set up a Linux swap area on a device or in a file.&lt;br /&gt;
&lt;br /&gt;
a) Log in as root user.&lt;br /&gt;
&lt;br /&gt;
b) Run this command to create 512MB swap file (1024 * 512MB = 524288 block size):&lt;br /&gt;
&lt;br /&gt;
# dd if=/dev/zero of=/swapf1 bs=1024 count=524288&lt;br /&gt;
&lt;br /&gt;
c) Set up a Linux swap area:&lt;br /&gt;
&lt;br /&gt;
# mkswap /swapf1&lt;br /&gt;
&lt;br /&gt;
d) Activate /swapfile1 swap space immediately:&lt;br /&gt;
&lt;br /&gt;
# swapon /swapf1&lt;br /&gt;
&lt;br /&gt;
e) To activate /swapf1 after Linux system reboot, add entry to /etc/fstab file. Open this file using text editor such as vi:&lt;br /&gt;
&lt;br /&gt;
# vi /etc/fstab&lt;br /&gt;
&lt;br /&gt;
Then,append following line:&lt;br /&gt;
&lt;br /&gt;
/swapf1 swap swap defaults 0 0&lt;br /&gt;
&lt;br /&gt;
So next time Linux comes up after reboot, it enables the new swap file for you automatically.&lt;br /&gt;
&lt;br /&gt;
Verifying if the swap is activated or not?&lt;br /&gt;
&lt;br /&gt;
$ free -m&lt;br /&gt;
&lt;br /&gt;
Hope the article proves useful for everyone who wants an extra swap space therein.</content><link rel='replies' type='application/atom+xml' href='http://linuxscoop.blogspot.com/feeds/2304800592853651239/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/need-to-add-extra-swap-space-read-this.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/2304800592853651239'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/2304800592853651239'/><link rel='alternate' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/need-to-add-extra-swap-space-read-this.html' title='Need to add extra swap space? Read this'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1019359938654970995.post-4594841076407588471</id><published>2011-01-02T06:13:00.000-08:00</published><updated>2011-01-02T06:14:40.452-08:00</updated><title type='text'>How to enable USB 3.0 support for Fedora 14</title><content type='html'>USB establish communication between devices and a host controller.It connects computer peripherals such as mouse, keyboards, digital cameras, printers, personal media players, flash drives, Network Adapters, and external hard drives.&lt;br /&gt;
&lt;br /&gt;
The original USB 1.0 specification had a data transfer rate of 12 Mbit/s.USB 2.0 had  a data transfer rate of 480 Mbit/s.USB 3.0 is a newly launched and has a specification of 4.8 Gbps.USB.It promises increased maximum bus power and increased device current draw to better accommodate power-hungry devices,New power management features and full-duplex data transfers and support for new transfer types.&lt;br /&gt;
&lt;br /&gt;
Fedora 14 includes the support of USB 3.0 but by default it comes disabled. Reason being it is preventing users from being able to suspend their laptops. USB 2.0 ports (ehci_hcd) works fine as expected. &lt;br /&gt;
&lt;br /&gt;
For anyone who need support for USB 3.0  and support for suspend/resume is not necessary, there is a workaround. Just pass the kernel parameter&lt;br /&gt;
&lt;br /&gt;
&lt;i&gt;xhci.enable=1&lt;/i&gt;&lt;br /&gt;
&lt;br /&gt;
This allows the xHCI support to load. There is also a workaround which will allow you to enable USB 3.0 support and still suspend successfully. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Next,create a file named &lt;i&gt;/etc/pm/config.d/xhci&lt;/i&gt;, with the contents:&lt;br /&gt;
&lt;br /&gt;
&lt;i&gt;SUSPEND_MODULES=&quot;xhci&quot;&lt;/i&gt;&lt;br /&gt;
&lt;br /&gt;
One can suspend and resume the system successfully.&lt;br /&gt;
&lt;br /&gt;
Hope it helps !!!</content><link rel='replies' type='application/atom+xml' href='http://linuxscoop.blogspot.com/feeds/4594841076407588471/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/how-to-enable-usb-30-support-for-fedora.html#comment-form' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/4594841076407588471'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1019359938654970995/posts/default/4594841076407588471'/><link rel='alternate' type='text/html' href='http://linuxscoop.blogspot.com/2011/01/how-to-enable-usb-30-support-for-fedora.html' title='How to enable USB 3.0 support for Fedora 14'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry></feed>