<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0"> <channel><title>Lynuxstuff.com</title> <link>http://www.lynuxstuff.com</link> <description /> <lastBuildDate>Mon, 17 Dec 2012 07:25:22 +0000</lastBuildDate> <language>en-US</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.5.1</generator> <atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/lynuxstuff" /><feedburner:info uri="lynuxstuff" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><creativeCommons:license>http://creativecommons.org/licenses/by-nd/3.0/</creativeCommons:license><image><link>http://creativecommons.org/licenses/by-nd/3.0/</link><url>http://creativecommons.org/images/public/somerights20.gif</url><title>Some Rights Reserved</title></image><feedburner:emailServiceId>lynuxstuff</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><item><title>SOSREPORT in Redhat Linux</title><link>http://feedproxy.google.com/~r/lynuxstuff/~3/M2qKet3BNNE/</link> <comments>http://www.lynuxstuff.com/sosreport/#comments</comments> <pubDate>Mon, 17 Dec 2012 07:25:22 +0000</pubDate> <dc:creator>LynuxStuff.com</dc:creator> <category><![CDATA[Applications]]></category> <category><![CDATA[redhat linux]]></category> <category><![CDATA[sosreport]]></category> <category><![CDATA[troubleshooting tools]]></category> <guid isPermaLink="false">http://www.lynuxstuff.com/?p=558</guid> <description>The sosreport is a tool that collects the configuration and diagnostic information from Redhat Enterprise Linux Machine. The  sosreport will collect information like the running kernel version, loaded modules,system configuration files and other system related information to archive file.&lt;img src="http://feeds.feedburner.com/~r/lynuxstuff/~4/M2qKet3BNNE" height="1" width="1"/&gt;</description> <wfw:commentRss>http://www.lynuxstuff.com/sosreport/feed/</wfw:commentRss> <slash:comments>0</slash:comments> <feedburner:origLink>http://www.lynuxstuff.com/sosreport/</feedburner:origLink></item> <item><title>RHEL 6 file permission with dot – File mode bit</title><link>http://feedproxy.google.com/~r/lynuxstuff/~3/N6Veamt8MMU/</link> <comments>http://www.lynuxstuff.com/rhel-6-file-permission-with-dot/#comments</comments> <pubDate>Wed, 28 Nov 2012 07:37:40 +0000</pubDate> <dc:creator>LynuxStuff.com</dc:creator> <category><![CDATA[OS Internals]]></category> <category><![CDATA[RHEL 6]]></category> <category><![CDATA[File mode bit]]></category> <guid isPermaLink="false">http://www.lynuxstuff.com/?p=546</guid> <description>The file mode bits is a single character that specifies  whether an alternate access method such as an access control list applies to the file.&lt;img src="http://feeds.feedburner.com/~r/lynuxstuff/~4/N6Veamt8MMU" height="1" width="1"/&gt;</description> <wfw:commentRss>http://www.lynuxstuff.com/rhel-6-file-permission-with-dot/feed/</wfw:commentRss> <slash:comments>0</slash:comments> <feedburner:origLink>http://www.lynuxstuff.com/rhel-6-file-permission-with-dot/</feedburner:origLink></item> <item><title>How to disable selinux</title><link>http://feedproxy.google.com/~r/lynuxstuff/~3/t9Yf0BQ0EfQ/</link> <comments>http://www.lynuxstuff.com/disable-selinux/#comments</comments> <pubDate>Fri, 23 Dec 2011 16:48:27 +0000</pubDate> <dc:creator>LynuxStuff.com</dc:creator> <category><![CDATA[Linux Security]]></category> <category><![CDATA[disable selinux]]></category> <category><![CDATA[Firewall settings in Linux]]></category> <category><![CDATA[How to disable selinux]]></category> <category><![CDATA[selinux enforcing mode]]></category> <category><![CDATA[selinux permissive mode]]></category> <guid isPermaLink="false">http://www.lynuxstuff.com/?p=507</guid> <description>In this article we are going to check how to disable SELinux in Centos Box.SELinux brings lot of security measures to your Linux box.It will provide an additional level of access control mechanism to files and folders on top of normal Linux security tools.&lt;img src="http://feeds.feedburner.com/~r/lynuxstuff/~4/t9Yf0BQ0EfQ" height="1" width="1"/&gt;</description> <wfw:commentRss>http://www.lynuxstuff.com/disable-selinux/feed/</wfw:commentRss> <slash:comments>1</slash:comments> <feedburner:origLink>http://www.lynuxstuff.com/disable-selinux/</feedburner:origLink></item> <item><title>Setting Up a Local yum Server</title><link>http://feedproxy.google.com/~r/lynuxstuff/~3/KAYgD8VXz1I/</link> <comments>http://www.lynuxstuff.com/local-yum-server/#comments</comments> <pubDate>Fri, 02 Dec 2011 18:20:05 +0000</pubDate> <dc:creator>LynuxStuff.com</dc:creator> <category><![CDATA[Applications]]></category> <category><![CDATA[Server Building]]></category> <category><![CDATA[rpm package manager]]></category> <category><![CDATA[Setting Up a Local yum Server]]></category> <category><![CDATA[yum package manager]]></category> <guid isPermaLink="false">http://www.lynuxstuff.com/?p=476</guid> <description>Sometimes you feel it is necessary or to be handy to have a local yum server in your network.So let's try to create a local yum server in your network.&lt;img src="http://feeds.feedburner.com/~r/lynuxstuff/~4/KAYgD8VXz1I" height="1" width="1"/&gt;</description> <wfw:commentRss>http://www.lynuxstuff.com/local-yum-server/feed/</wfw:commentRss> <slash:comments>0</slash:comments> <feedburner:origLink>http://www.lynuxstuff.com/local-yum-server/</feedburner:origLink></item> <item><title>Using yum with a proxy server</title><link>http://feedproxy.google.com/~r/lynuxstuff/~3/sXQZTDJt2WU/</link> <comments>http://www.lynuxstuff.com/yum-with-proxy-server/#comments</comments> <pubDate>Tue, 22 Nov 2011 16:23:52 +0000</pubDate> <dc:creator>LynuxStuff.com</dc:creator> <category><![CDATA[Basic Setup]]></category> <category><![CDATA[Troubleshooting]]></category> <category><![CDATA[how to configure yum to use proxy server]]></category> <category><![CDATA[how to pass proxyserver from commandline]]></category> <category><![CDATA[squid configurations]]></category> <category><![CDATA[using yum with proxy server]]></category> <guid isPermaLink="false">http://www.lynuxstuff.com/?p=462</guid> <description>This how to article for using yum with a proxy server describe how to configure YUM to work behind proxy server using username and password.If you are  behind proxy server then you need to configure yum to pass proxy server.&lt;img src="http://feeds.feedburner.com/~r/lynuxstuff/~4/sXQZTDJt2WU" height="1" width="1"/&gt;</description> <wfw:commentRss>http://www.lynuxstuff.com/yum-with-proxy-server/feed/</wfw:commentRss> <slash:comments>0</slash:comments> <feedburner:origLink>http://www.lynuxstuff.com/yum-with-proxy-server/</feedburner:origLink></item> <item><title>Server Configuration checking commands</title><link>http://feedproxy.google.com/~r/lynuxstuff/~3/ImaUWFAONnU/</link> <comments>http://www.lynuxstuff.com/server-configuration-checking-commands/#comments</comments> <pubDate>Sat, 19 Nov 2011 15:29:47 +0000</pubDate> <dc:creator>LynuxStuff.com</dc:creator> <category><![CDATA[Basic Setup]]></category> <category><![CDATA[Server Building]]></category> <category><![CDATA[configtest]]></category> <category><![CDATA[dhcpd]]></category> <category><![CDATA[httpd]]></category> <category><![CDATA[squid configurations]]></category> <category><![CDATA[testparm]]></category> <guid isPermaLink="false">http://www.lynuxstuff.com/?p=456</guid> <description>Linux server configuration file checking commands in brief.These commands are useful for verifying configuration files in Linux server before applying to the server.&lt;img src="http://feeds.feedburner.com/~r/lynuxstuff/~4/ImaUWFAONnU" height="1" width="1"/&gt;</description> <wfw:commentRss>http://www.lynuxstuff.com/server-configuration-checking-commands/feed/</wfw:commentRss> <slash:comments>0</slash:comments> <feedburner:origLink>http://www.lynuxstuff.com/server-configuration-checking-commands/</feedburner:origLink></item> <item><title>7 important uses of LSOF Command for Linux admin</title><link>http://feedproxy.google.com/~r/lynuxstuff/~3/p-WGX8ZmNCA/</link> <comments>http://www.lynuxstuff.com/7-important-uses-of-lsof-command-for-linux-admin/#comments</comments> <pubDate>Thu, 10 Nov 2011 20:48:09 +0000</pubDate> <dc:creator>LynuxStuff.com</dc:creator> <category><![CDATA[Applications]]></category> <category><![CDATA[OS Internals]]></category> <category><![CDATA[Troubleshooting]]></category> <category><![CDATA[Linux administration commands]]></category> <category><![CDATA[lsof command]]></category> <category><![CDATA[troubleshooting commands in Linux]]></category> <guid isPermaLink="false">http://www.lynuxstuff.com/?p=433</guid> <description>important uses of LSOF Command - lsof is a Linux utility which lists the information about files opened by processes.LSOF is one of the powerful  tool available for troubleshooting problems.&lt;img src="http://feeds.feedburner.com/~r/lynuxstuff/~4/p-WGX8ZmNCA" height="1" width="1"/&gt;</description> <wfw:commentRss>http://www.lynuxstuff.com/7-important-uses-of-lsof-command-for-linux-admin/feed/</wfw:commentRss> <slash:comments>1</slash:comments> <feedburner:origLink>http://www.lynuxstuff.com/7-important-uses-of-lsof-command-for-linux-admin/</feedburner:origLink></item> <item><title>Configure NAT in  Linux box using IPTABLES</title><link>http://feedproxy.google.com/~r/lynuxstuff/~3/u9bqBMsXx74/</link> <comments>http://www.lynuxstuff.com/configure-nat-in-linux-box-using-iptables/#comments</comments> <pubDate>Sun, 23 Oct 2011 14:29:19 +0000</pubDate> <dc:creator>LynuxStuff.com</dc:creator> <category><![CDATA[Linux Security]]></category> <category><![CDATA[Networking]]></category> <category><![CDATA[how to configure Linux box as router]]></category> <category><![CDATA[Ip forwarding in Linux]]></category> <category><![CDATA[iprouting in Linux]]></category> <guid isPermaLink="false">http://www.lynuxstuff.com/?p=428</guid> <description>NAT-Network Address Translation is used to communicate from one network to other network with different sub-net.So your Linux box will act as a gateway and will allow to communicate between two different networks.&lt;img src="http://feeds.feedburner.com/~r/lynuxstuff/~4/u9bqBMsXx74" height="1" width="1"/&gt;</description> <wfw:commentRss>http://www.lynuxstuff.com/configure-nat-in-linux-box-using-iptables/feed/</wfw:commentRss> <slash:comments>0</slash:comments> <feedburner:origLink>http://www.lynuxstuff.com/configure-nat-in-linux-box-using-iptables/</feedburner:origLink></item> <item><title>Convert Linux man pages to PDF</title><link>http://feedproxy.google.com/~r/lynuxstuff/~3/xe9Ob37DWvw/</link> <comments>http://www.lynuxstuff.com/convert-linux-man-pages-to-pdf/#comments</comments> <pubDate>Fri, 02 Sep 2011 19:06:51 +0000</pubDate> <dc:creator>LynuxStuff.com</dc:creator> <category><![CDATA[Applications]]></category> <category><![CDATA[Scripting & Automation]]></category> <category><![CDATA[Convert Linux man pages to PDF]]></category> <category><![CDATA[manpages]]></category> <category><![CDATA[ps2pdf]]></category> <guid isPermaLink="false">http://www.lynuxstuff.com/?p=420</guid> <description>Here we are trying to find out how to convert Linux man pages to PDF. Man Pages are most reliable reference available for Linux users and man command remains the easiest way to access those reference pages.&lt;img src="http://feeds.feedburner.com/~r/lynuxstuff/~4/xe9Ob37DWvw" height="1" width="1"/&gt;</description> <wfw:commentRss>http://www.lynuxstuff.com/convert-linux-man-pages-to-pdf/feed/</wfw:commentRss> <slash:comments>0</slash:comments> <feedburner:origLink>http://www.lynuxstuff.com/convert-linux-man-pages-to-pdf/</feedburner:origLink></item> <item><title>Manage password aging in Linux systems</title><link>http://feedproxy.google.com/~r/lynuxstuff/~3/rGyCkbP8KiU/</link> <comments>http://www.lynuxstuff.com/manage-password-aging-in-linux-systems/#comments</comments> <pubDate>Fri, 26 Aug 2011 23:38:11 +0000</pubDate> <dc:creator>LynuxStuff.com</dc:creator> <category><![CDATA[Linux Security]]></category> <category><![CDATA[Set password expiry for users]]></category> <category><![CDATA[User management]]></category> <guid isPermaLink="false">http://www.lynuxstuff.com/?p=414</guid> <description>password expiry for users is configuring in /etc/login.defs file.These are the password aging parameters PASS_MAX_DAYS                Maximum number of days a password may be used. PASS_MIN_DAYS                 Minimum number of days allowed between password changes. PASS_WARN_AGE               Number of days warning given before a password expires. By default PASS_MAX_DAYS will be 99999 days that means no password expiry.So we are going to configure password expiry for all users in 90 days and minimum days between password change is 1 day. Open /etc/login.defs and [...]&lt;img src="http://feeds.feedburner.com/~r/lynuxstuff/~4/rGyCkbP8KiU" height="1" width="1"/&gt;</description> <wfw:commentRss>http://www.lynuxstuff.com/manage-password-aging-in-linux-systems/feed/</wfw:commentRss> <slash:comments>0</slash:comments> <feedburner:origLink>http://www.lynuxstuff.com/manage-password-aging-in-linux-systems/</feedburner:origLink></item> <item><title>Autoconf – brief introduction for beginners</title><link>http://feedproxy.google.com/~r/lynuxstuff/~3/7WsXMVXtLik/</link> <comments>http://www.lynuxstuff.com/autoconf-brief-introduction-for-beginners/#comments</comments> <pubDate>Thu, 25 Aug 2011 23:59:03 +0000</pubDate> <dc:creator>LynuxStuff.com</dc:creator> <category><![CDATA[Applications]]></category> <category><![CDATA[OS Internals]]></category> <category><![CDATA[Scripting & Automation]]></category> <category><![CDATA[autoconf]]></category> <category><![CDATA[automake]]></category> <category><![CDATA[GNU tools]]></category> <category><![CDATA[Linux development tools]]></category> <guid isPermaLink="false">http://www.lynuxstuff.com/?p=409</guid> <description>Autoconf is a set of tools which makes your project configurable and portable for running in Linux distributions. Simply, autoconf will help you to create configure script and Makefile for your code. Before going to generate configure script using autoconf, we need to define set of rules and dependencies. We are defining that rules and dependencies in two files, configure.in and Makefile.in. Create default Makefile and keep in project directory.We can genarate the configure.in based on the rules specified in [...]&lt;img src="http://feeds.feedburner.com/~r/lynuxstuff/~4/7WsXMVXtLik" height="1" width="1"/&gt;</description> <wfw:commentRss>http://www.lynuxstuff.com/autoconf-brief-introduction-for-beginners/feed/</wfw:commentRss> <slash:comments>0</slash:comments> <feedburner:origLink>http://www.lynuxstuff.com/autoconf-brief-introduction-for-beginners/</feedburner:origLink></item> <item><title>EXIM Mail Server on CENTOS</title><link>http://feedproxy.google.com/~r/lynuxstuff/~3/J7VywZDkabM/</link> <comments>http://www.lynuxstuff.com/exim-mail-server-on-centos/#comments</comments> <pubDate>Wed, 24 Aug 2011 22:49:03 +0000</pubDate> <dc:creator>LynuxStuff.com</dc:creator> <category><![CDATA[Server Building]]></category> <category><![CDATA[EXIM Mail Server on CENTOS]]></category> <category><![CDATA[mail server configuration]]></category> <guid isPermaLink="false">http://www.lynuxstuff.com/?p=339</guid> <description>Steps: #yum install exim system-switch-mail After successful installation, we need to make some necessary configurations. Switch default MTA(Mail Transfer agent) to exim if it is sendmail or any other application by using system-switch-mail. Then stop sendmail service if it is running and disable in startup. #service sendmail stop #chkconfig  sendmail off And start exim service and enable to start at boot time #service exim start #chkconfig exim on If you want to enable manual routing for mail then ,add  the [...]&lt;img src="http://feeds.feedburner.com/~r/lynuxstuff/~4/J7VywZDkabM" height="1" width="1"/&gt;</description> <wfw:commentRss>http://www.lynuxstuff.com/exim-mail-server-on-centos/feed/</wfw:commentRss> <slash:comments>0</slash:comments> <feedburner:origLink>http://www.lynuxstuff.com/exim-mail-server-on-centos/</feedburner:origLink></item> <item><title>How to disable ping requests in Linux box</title><link>http://feedproxy.google.com/~r/lynuxstuff/~3/OEbudP_cqPM/</link> <comments>http://www.lynuxstuff.com/how-to-disable-ping-requests-in-linux-box/#comments</comments> <pubDate>Sun, 07 Aug 2011 17:27:53 +0000</pubDate> <dc:creator>LynuxStuff.com</dc:creator> <category><![CDATA[OS Internals]]></category> <category><![CDATA[block icmp]]></category> <category><![CDATA[how to disable ping requests in Linux box]]></category> <category><![CDATA[how to reload kernel parameters in runtime]]></category> <guid isPermaLink="false">http://www.lynuxstuff.com/?p=398</guid> <description>The basic network discovery always start with ping utility.So blocking the ping requests will make the system discovery difficult.To disable ping requests ,we just need to add/modify some kernel parameters. What we are doing here is the permanent change. So open /etc/sysctl.conf  and add the following line to /etc/sysctl.conf net.ipv4.icmp_echo_ignore_all = 1 And reload kernel parameters using command sysctl -p (sysctl -p is used to reload kernel parameters at runtime). After successful configuration,if any one try to ping your server [...]&lt;img src="http://feeds.feedburner.com/~r/lynuxstuff/~4/OEbudP_cqPM" height="1" width="1"/&gt;</description> <wfw:commentRss>http://www.lynuxstuff.com/how-to-disable-ping-requests-in-linux-box/feed/</wfw:commentRss> <slash:comments>1</slash:comments> <feedburner:origLink>http://www.lynuxstuff.com/how-to-disable-ping-requests-in-linux-box/</feedburner:origLink></item> <item><title>Centralized log host using Syslog</title><link>http://feedproxy.google.com/~r/lynuxstuff/~3/WyxYc2ctSxo/</link> <comments>http://www.lynuxstuff.com/centralized-log-host-using-syslog/#comments</comments> <pubDate>Sat, 06 Aug 2011 07:45:15 +0000</pubDate> <dc:creator>LynuxStuff.com</dc:creator> <category><![CDATA[OS Internals]]></category> <category><![CDATA[Server Building]]></category> <category><![CDATA[Central log server]]></category> <category><![CDATA[Centralized log host using Syslog]]></category> <category><![CDATA[Syslog]]></category> <guid isPermaLink="false">http://www.lynuxstuff.com/?p=380</guid> <description>Building a centralized log host in your network will ease the process of troubleshooting your servers from a single window.Centralized log host will accepts all the log messages from client and store in that server.&lt;img src="http://feeds.feedburner.com/~r/lynuxstuff/~4/WyxYc2ctSxo" height="1" width="1"/&gt;</description> <wfw:commentRss>http://www.lynuxstuff.com/centralized-log-host-using-syslog/feed/</wfw:commentRss> <slash:comments>0</slash:comments> <feedburner:origLink>http://www.lynuxstuff.com/centralized-log-host-using-syslog/</feedburner:origLink></item> <item><title>10 basic commands a system admin need to know</title><link>http://feedproxy.google.com/~r/lynuxstuff/~3/SpaLX1Mhrf8/</link> <comments>http://www.lynuxstuff.com/10-basic-commands-a-system-admin-need-to-know/#comments</comments> <pubDate>Fri, 29 Jul 2011 21:12:42 +0000</pubDate> <dc:creator>LynuxStuff.com</dc:creator> <category><![CDATA[Basic Setup]]></category> <category><![CDATA[10 basic commands a system admin need to know]]></category> <category><![CDATA[Linux basic commands]]></category> <guid isPermaLink="false">http://www.lynuxstuff.com/?p=372</guid> <description>tty &amp;#8211; tty command  will tells you current terminal. #tty /dev/pts/1 whoami- whoami commands tells you current logged-in username #whoami root which- which command will give you the path of the command #which tty /usr/bin/tty set- set command prints and sets the shell variables or environment variables echo-echo command will prints the output to screen #echo $PWD print current working directory to the screen. history-history command will tells you the command history clear or ctrl+l- This will clear the terminal [...]&lt;img src="http://feeds.feedburner.com/~r/lynuxstuff/~4/SpaLX1Mhrf8" height="1" width="1"/&gt;</description> <wfw:commentRss>http://www.lynuxstuff.com/10-basic-commands-a-system-admin-need-to-know/feed/</wfw:commentRss> <slash:comments>0</slash:comments> <feedburner:origLink>http://www.lynuxstuff.com/10-basic-commands-a-system-admin-need-to-know/</feedburner:origLink></item> <item><title>Environment Variables in Unix</title><link>http://feedproxy.google.com/~r/lynuxstuff/~3/Y10E1uxH7H0/</link> <comments>http://www.lynuxstuff.com/unix-environment-variables/#comments</comments> <pubDate>Tue, 12 Jul 2011 19:28:04 +0000</pubDate> <dc:creator>LynuxStuff.com</dc:creator> <category><![CDATA[Applications]]></category> <category><![CDATA[OS Internals]]></category> <category><![CDATA[environment variables in Linux]]></category> <category><![CDATA[Ksh]]></category> <category><![CDATA[set or view UNIX environment variable for Csh]]></category> <category><![CDATA[Tcsh and Bourne shell using commands]]></category> <guid isPermaLink="false">http://www.lynuxstuff.com/?p=366</guid> <description>Environment variables in Unix are a set of dynamic named values that can affect the way running processes will be have on a computer&lt;img src="http://feeds.feedburner.com/~r/lynuxstuff/~4/Y10E1uxH7H0" height="1" width="1"/&gt;</description> <wfw:commentRss>http://www.lynuxstuff.com/unix-environment-variables/feed/</wfw:commentRss> <slash:comments>1</slash:comments> <feedburner:origLink>http://www.lynuxstuff.com/unix-environment-variables/</feedburner:origLink></item> <item><title>How to record a UNIX terminal session</title><link>http://feedproxy.google.com/~r/lynuxstuff/~3/JLxnHaS-Vrg/</link> <comments>http://www.lynuxstuff.com/how-to-record-a-unix-terminal-session/#comments</comments> <pubDate>Sat, 09 Jul 2011 17:24:06 +0000</pubDate> <dc:creator>LynuxStuff.com</dc:creator> <category><![CDATA[Applications]]></category> <category><![CDATA[record unix terminal session]]></category> <category><![CDATA[script command]]></category> <category><![CDATA[Terminal logging]]></category> <guid isPermaLink="false">http://www.lynuxstuff.com/?p=362</guid> <description>script is one of the powerful tool available to record a unix terminal session.Start the recording of Unix terminal session with script command.And start doing your important configurations, it will recorded in a file. After completing the task ,you can exit the recording with exit command Example procedure: [root@core-22 ~]# script Script started, file is typescript [root@core-22 ~]# service httpd stop Stopping httpd:                                            [  OK  ] [root@core-22 ~]# service httpd start Starting httpd:                                            [  OK  ] [root@core-22 ~]# exit exit [...]&lt;img src="http://feeds.feedburner.com/~r/lynuxstuff/~4/JLxnHaS-Vrg" height="1" width="1"/&gt;</description> <wfw:commentRss>http://www.lynuxstuff.com/how-to-record-a-unix-terminal-session/feed/</wfw:commentRss> <slash:comments>0</slash:comments> <feedburner:origLink>http://www.lynuxstuff.com/how-to-record-a-unix-terminal-session/</feedburner:origLink></item> <item><title>How to find current system runlevel</title><link>http://feedproxy.google.com/~r/lynuxstuff/~3/6Ugt68M81UQ/</link> <comments>http://www.lynuxstuff.com/how-to-find-current-system-runlevel/#comments</comments> <pubDate>Sat, 09 Jul 2011 07:19:42 +0000</pubDate> <dc:creator>LynuxStuff.com</dc:creator> <category><![CDATA[OS Internals]]></category> <category><![CDATA[find current runlevel in Linux]]></category> <category><![CDATA[inittab file in Linux]]></category> <category><![CDATA[what is runlevel]]></category> <guid isPermaLink="false">http://www.lynuxstuff.com/?p=350</guid> <description>What is run level in Unix??? Run level defines the predefined set of operational state for Unix system.The operational state is defined in file  inittab which is located in /etc. init command used to switch between different run levels.init command followed by runlevel will switch system to corresponding runlevel Eg:  init 3 This will switch system to run level 3 which is text mode. Standard Linux distributions have the following run levels: No Name Description 0 Halt System will go [...]&lt;img src="http://feeds.feedburner.com/~r/lynuxstuff/~4/6Ugt68M81UQ" height="1" width="1"/&gt;</description> <wfw:commentRss>http://www.lynuxstuff.com/how-to-find-current-system-runlevel/feed/</wfw:commentRss> <slash:comments>2</slash:comments> <feedburner:origLink>http://www.lynuxstuff.com/how-to-find-current-system-runlevel/</feedburner:origLink></item> <item><title>Boot Linux GRUB into single user mode</title><link>http://feedproxy.google.com/~r/lynuxstuff/~3/Gi1QyjRVzDQ/</link> <comments>http://www.lynuxstuff.com/boot-linux-grub-into-single-user-mode/#comments</comments> <pubDate>Fri, 08 Jul 2011 18:21:05 +0000</pubDate> <dc:creator>LynuxStuff.com</dc:creator> <category><![CDATA[OS Internals]]></category> <category><![CDATA[Troubleshooting]]></category> <category><![CDATA[boot linux into single user mode]]></category> <category><![CDATA[how to recover root password in Linux]]></category> <guid isPermaLink="false">http://www.lynuxstuff.com/?p=341</guid> <description>First runlevel for Linux system which only one user is allowed to access that root user.Single user mode is useful for fixing some system problem like filesystem errors,recovering root password etc.So these are the steps for entering to single user mode in Linux.This is based on redhat enterprise linux 5( RHEL 5) Steps: Press any key during booting to go to OS listing Hit &amp;#8216;e&amp;#8216; to edit the selected command in the boot sequence(Read the specified instructions in bottom of [...]&lt;img src="http://feeds.feedburner.com/~r/lynuxstuff/~4/Gi1QyjRVzDQ" height="1" width="1"/&gt;</description> <wfw:commentRss>http://www.lynuxstuff.com/boot-linux-grub-into-single-user-mode/feed/</wfw:commentRss> <slash:comments>1</slash:comments> <feedburner:origLink>http://www.lynuxstuff.com/boot-linux-grub-into-single-user-mode/</feedburner:origLink></item> <item><title>PAM-Plugable Authentication Modules</title><link>http://feedproxy.google.com/~r/lynuxstuff/~3/S-FIq2d-OgU/</link> <comments>http://www.lynuxstuff.com/pam-plugable-authentication-modules/#comments</comments> <pubDate>Fri, 01 Jul 2011 09:54:59 +0000</pubDate> <dc:creator>LynuxStuff.com</dc:creator> <category><![CDATA[Glossaries]]></category> <category><![CDATA[Linux authentication scheme]]></category> <category><![CDATA[pam.d]]></category> <guid isPermaLink="false">http://www.networkscope.com/lynuxstuff.com/?p=336</guid> <description>PAM is an authentication layer that allows programs to be written independent of specific authentication scheme.The application request authentication via the PAM library  and PAM library determines whether the user is allowed to proceed.If an administrator wants to implement a different authentication,he just change the PAM configuration files and existing program work seamlessly. All application and services that depend on PAM for authentication have a file in /etc/pam.d/ directory with filename being exactly the same as the application or service.The [...]&lt;img src="http://feeds.feedburner.com/~r/lynuxstuff/~4/S-FIq2d-OgU" height="1" width="1"/&gt;</description> <wfw:commentRss>http://www.lynuxstuff.com/pam-plugable-authentication-modules/feed/</wfw:commentRss> <slash:comments>0</slash:comments> <feedburner:origLink>http://www.lynuxstuff.com/pam-plugable-authentication-modules/</feedburner:origLink></item> </channel> </rss>
