<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	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/"
	>

<channel>
	<title>KrazyWorks&#187; Commands &amp; Shells</title>
	<atom:link href="http://www.krazyworks.com/category/sysadmin/commands-and-shells/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.krazyworks.com</link>
	<description>Networking, Systems Design, and Disaster Recovery</description>
	<lastBuildDate>Thu, 09 Feb 2012 14:47:19 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Compress Old Log Files on Linux</title>
		<link>http://www.krazyworks.com/compress-old-log-files-on-linux/</link>
		<comments>http://www.krazyworks.com/compress-old-log-files-on-linux/#comments</comments>
		<pubDate>Thu, 12 Jan 2012 22:06:20 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Commands & Shells]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=2677</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/commands-and-shells/" title="Commands &amp; Shells">Commands &amp; Shells</a></p>
Most log files located in /var/log are part of the log rotation and will be compressed automatically. However, in many cases various user applications maintain log files outside of /var/log. These logs are not managed ...]]></description>
		<wfw:commentRss>http://www.krazyworks.com/compress-old-log-files-on-linux/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Testing SSH Connectivity to Multiple Servers</title>
		<link>http://www.krazyworks.com/testing-ssh-connectivity-to-multiple-servers/</link>
		<comments>http://www.krazyworks.com/testing-ssh-connectivity-to-multiple-servers/#comments</comments>
		<pubDate>Tue, 27 Dec 2011 06:46:39 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Commands & Shells]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=2559</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/commands-and-shells/" title="Commands &amp; Shells">Commands &amp; Shells</a></p>Imagine a hypothetical scenario: you support hundreds of remote servers and you need to check which server you can access via SSH and which servers are not letting you log in. Doing this manually is a tedious process that many sysadmins choose to skip. The inevitable outcome is inability to quickly access a system when it really counts.]]></description>
		<wfw:commentRss>http://www.krazyworks.com/testing-ssh-connectivity-to-multiple-servers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Writing a Linux Startup Script</title>
		<link>http://www.krazyworks.com/writing-a-linux-startup-script/</link>
		<comments>http://www.krazyworks.com/writing-a-linux-startup-script/#comments</comments>
		<pubDate>Fri, 16 Dec 2011 06:11:47 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Commands & Shells]]></category>
		<category><![CDATA[Featured]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=2615</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/commands-and-shells/" title="Commands &amp; Shells">Commands &amp; Shells</a><a href="http://www.krazyworks.com/category/featured/" title="Featured">Featured</a></p>As basic as the task of creating a startup script may sound, even experienced sysadmins sometimes run into problems with having services start at the right time during the boot process or stop during the shutdown. Two major reasons for this: the procedure is a bit convoluted due to linking. Also, writing startup scripts is not something you have to do very often these days.]]></description>
		<wfw:commentRss>http://www.krazyworks.com/writing-a-linux-startup-script/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Viewing &#8220;man&#8221; Pages in a Web Browser</title>
		<link>http://www.krazyworks.com/viewing-man-pages-in-a-web-browser/</link>
		<comments>http://www.krazyworks.com/viewing-man-pages-in-a-web-browser/#comments</comments>
		<pubDate>Fri, 16 Sep 2011 04:43:16 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Commands & Shells]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=2502</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/commands-and-shells/" title="Commands &amp; Shells">Commands &amp; Shells</a></p>The Unix "man" pages are an indispensable tool even for the most experienced of sysadmins. Unfortunately, in a terminal window the text may be hard to read and getting a hard copy to take with you down to the datacenter will really test your Unix skills. The following quick script will convert the "man" page of your choice into formatted text and open it in the Web browser.]]></description>
		<wfw:commentRss>http://www.krazyworks.com/viewing-man-pages-in-a-web-browser/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Autorebooting Servers on Low or High Load</title>
		<link>http://www.krazyworks.com/autorebooting-servers-on-low-or-high-load/</link>
		<comments>http://www.krazyworks.com/autorebooting-servers-on-low-or-high-load/#comments</comments>
		<pubDate>Wed, 14 Sep 2011 21:03:14 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Commands & Shells]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=2499</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/commands-and-shells/" title="Commands &amp; Shells">Commands &amp; Shells</a></p>Recently I ran into a situation where I needed to reboot several HPC cluster compute nodes. A couple of systems were still running user jobs that I did not want to interrupt. I also didn't want to sit around and watch those jobs, as there was not way of telling how long they could take to complete. The solution was to write a short script that looks something like this...]]></description>
		<wfw:commentRss>http://www.krazyworks.com/autorebooting-servers-on-low-or-high-load/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Testing RAM in Linux</title>
		<link>http://www.krazyworks.com/testing-ram-from-linux/</link>
		<comments>http://www.krazyworks.com/testing-ram-from-linux/#comments</comments>
		<pubDate>Fri, 02 Sep 2011 15:42:08 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Commands & Shells]]></category>
		<category><![CDATA[Featured]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=2473</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/commands-and-shells/" title="Commands &amp; Shells">Commands &amp; Shells</a><a href="http://www.krazyworks.com/category/featured/" title="Featured">Featured</a></p>A number of good and mostly free tools are available for testing RAM hardware. However, most of these applications are designed to operate in stand-alone mode that requires shutting down the OS. Still, tare a few ways to run memory integrity checks from inside the operating environment. Here we will look at using dd and memtester.]]></description>
		<wfw:commentRss>http://www.krazyworks.com/testing-ram-from-linux/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using Expect with SSH and Su</title>
		<link>http://www.krazyworks.com/using-expect-with-ssh-and-su/</link>
		<comments>http://www.krazyworks.com/using-expect-with-ssh-and-su/#comments</comments>
		<pubDate>Mon, 29 Aug 2011 14:47:08 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Commands & Shells]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=2461</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/commands-and-shells/" title="Commands &amp; Shells">Commands &amp; Shells</a></p>We have discussed using expect with sudo in an SSH session. Another common way to run commands on remote servers as root is to use the su - root command, where sudo is not configured. The trick to automating su operations using expect is to launch the su command with the spawn ssh command.]]></description>
		<wfw:commentRss>http://www.krazyworks.com/using-expect-with-ssh-and-su/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Moving Average with Excel and Shell Script</title>
		<link>http://www.krazyworks.com/moving-average-with-excel-and-shell-script/</link>
		<comments>http://www.krazyworks.com/moving-average-with-excel-and-shell-script/#comments</comments>
		<pubDate>Thu, 11 Aug 2011 16:41:54 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Commands & Shells]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=2441</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/commands-and-shells/" title="Commands &amp; Shells">Commands &amp; Shells</a></p>In this example we will show you how to calculate simple moving average using Excel and a shell script. As more data is added to the file, the shell script and the Excel formula will automatically use the specified number of the latest data points to calculate the moving average.]]></description>
		<wfw:commentRss>http://www.krazyworks.com/moving-average-with-excel-and-shell-script/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Configuring Passwordless SSH</title>
		<link>http://www.krazyworks.com/configuring-passwordless-ssh/</link>
		<comments>http://www.krazyworks.com/configuring-passwordless-ssh/#comments</comments>
		<pubDate>Sat, 23 Jul 2011 15:02:39 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Commands & Shells]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=2425</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/commands-and-shells/" title="Commands &amp; Shells">Commands &amp; Shells</a></p>Passwordless SSH works by pre-sharing public encryption keys. It is important to understand that setting up passwordless SSH opens your servers to certain security risks. A compromised user account on one server may allow the attacker to gain access to multiple systems on the network. Try to avoid using passwordless access for accounts with elevated privileges.]]></description>
		<wfw:commentRss>http://www.krazyworks.com/configuring-passwordless-ssh/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Automating SSH and Sudo with Expect</title>
		<link>http://www.krazyworks.com/automating-ssh-and-sudo-with-expect/</link>
		<comments>http://www.krazyworks.com/automating-ssh-and-sudo-with-expect/#comments</comments>
		<pubDate>Thu, 14 Jul 2011 14:20:57 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Commands & Shells]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=2417</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/commands-and-shells/" title="Commands &amp; Shells">Commands &amp; Shells</a></p>Let's imagine a hypothetical scenario: you have a list of a hundred Linux servers and you need to log into each one of them and remove a local user "roger" and his home directory. Doing this by hand will get tedious and, chances are, you will make a few typos and there will be some collateral damage. ]]></description>
		<wfw:commentRss>http://www.krazyworks.com/automating-ssh-and-sudo-with-expect/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Run Background Tasks via SSH</title>
		<link>http://www.krazyworks.com/run-background-tasks-via-ssh/</link>
		<comments>http://www.krazyworks.com/run-background-tasks-via-ssh/#comments</comments>
		<pubDate>Thu, 16 Jun 2011 04:58:48 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Commands & Shells]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=2377</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/commands-and-shells/" title="Commands &amp; Shells">Commands &amp; Shells</a></p>The idea here is simple: you need to connect to hosts 1..100 and execute a command in the background. The trick is to make sure the command continues to run after the SSH session terminates. Simply adding the "&#038;" at the end of the command is not the answer here.]]></description>
		<wfw:commentRss>http://www.krazyworks.com/run-background-tasks-via-ssh/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Password-less SSH and Autofs</title>
		<link>http://www.krazyworks.com/password-less-ssh-and-autofs/</link>
		<comments>http://www.krazyworks.com/password-less-ssh-and-autofs/#comments</comments>
		<pubDate>Sun, 15 May 2011 08:04:36 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Commands & Shells]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=2351</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/commands-and-shells/" title="Commands &amp; Shells">Commands &amp; Shells</a></p>Recently I've ran into an unusual problem with SSH on SLES 11 SP1. The system - a small HPC cluster - is configured to use NIS for authentication and automounter maps. Whenever a user logs in, the home directory is automounted from an external NAS. Each user has a ~/.ssh directory with the authorized_keys2 and known_hosts required for password-less SSH access among the cluster nodes.]]></description>
		<wfw:commentRss>http://www.krazyworks.com/password-less-ssh-and-autofs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Force NTP Time Update on Linux</title>
		<link>http://www.krazyworks.com/force-ntp-time-update-on-linux/</link>
		<comments>http://www.krazyworks.com/force-ntp-time-update-on-linux/#comments</comments>
		<pubDate>Tue, 22 Feb 2011 00:36:40 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Commands & Shells]]></category>
		<category><![CDATA[force ntp]]></category>
		<category><![CDATA[force time sync]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[ntp]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=2282</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/commands-and-shells/" title="Commands &amp; Shells">Commands &amp; Shells</a></p>Imagine this: you created the /etc/ntp.conf file, enabled and started the ntpd service, and... the system time is still off. Is there a way to force time sync with the NTP server? It must be your lucky day. All you have to do is to connect to your box as root and run the following command...]]></description>
		<wfw:commentRss>http://www.krazyworks.com/force-ntp-time-update-on-linux/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Find Command with Multiple Exec Statements</title>
		<link>http://www.krazyworks.com/find-command-with-multiple-exec-statements/</link>
		<comments>http://www.krazyworks.com/find-command-with-multiple-exec-statements/#comments</comments>
		<pubDate>Thu, 10 Feb 2011 04:32:58 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Commands & Shells]]></category>
		<category><![CDATA[exec]]></category>
		<category><![CDATA[find]]></category>
		<category><![CDATA[multiple]]></category>
		<category><![CDATA[numeric permissions]]></category>
		<category><![CDATA[shell]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=2239</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/commands-and-shells/" title="Commands &amp; Shells">Commands &amp; Shells</a></p>This is a very simple one, but somehow I always forget the correct syntax. I want to use the "find" command to locate files and then use several "exec" statements to perform various operations on whatever "find" finds. In the following example I am making sure that all /etc/*.conf files are owned by root and that they don't have permissions greater than 644.]]></description>
		<wfw:commentRss>http://www.krazyworks.com/find-command-with-multiple-exec-statements/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Modifying Solaris Services</title>
		<link>http://www.krazyworks.com/modifying-solaris-services/</link>
		<comments>http://www.krazyworks.com/modifying-solaris-services/#comments</comments>
		<pubDate>Thu, 09 Sep 2010 20:33:22 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Commands & Shells]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=2109</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/commands-and-shells/" title="Commands &amp; Shells">Commands &amp; Shells</a></p>Recently I ran into an issue: the sshd service on a Solaris 10 box needed to be used with a custom configuration file. By default, the sshd service will use /etc/ssh/sshd_config. I needed it to use /etc/ssh/sshd_config_custom. I could not just modify the default configuration file. Don't ask why - it's complicated. So here's what I ended up doing and this process is applicable to modifying any other Solaris 10 (and above) service.]]></description>
		<wfw:commentRss>http://www.krazyworks.com/modifying-solaris-services/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Substitute Commands Depending on User ID</title>
		<link>http://www.krazyworks.com/substitute-commands-depending-on-user-id/</link>
		<comments>http://www.krazyworks.com/substitute-commands-depending-on-user-id/#comments</comments>
		<pubDate>Thu, 09 Sep 2010 18:44:00 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Commands & Shells]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=2104</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/commands-and-shells/" title="Commands &amp; Shells">Commands &amp; Shells</a></p>Here is a quick example of how to substitute system commands based on who tries to run them. A customer of mine has recently deployed a security audit application on his servers. The application has a few bugs that the vendor has not yet resolved. For example, the security audit agent looks at the output of the "mount" command to see if any filesystems are mounted without the "nosuid" option.]]></description>
		<wfw:commentRss>http://www.krazyworks.com/substitute-commands-depending-on-user-id/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>NFS &#8220;Not Owner&#8221; Error</title>
		<link>http://www.krazyworks.com/nfs-not-owner-error/</link>
		<comments>http://www.krazyworks.com/nfs-not-owner-error/#comments</comments>
		<pubDate>Tue, 31 Aug 2010 03:34:52 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Commands & Shells]]></category>
		<category><![CDATA[Filesystems]]></category>
		<category><![CDATA[Networking]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=2077</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/commands-and-shells/" title="Commands &amp; Shells">Commands &amp; Shells</a><a href="http://www.krazyworks.com/category/sysadmin/data/filesystems/" title="Filesystems">Filesystems</a><a href="http://www.krazyworks.com/category/sysadmin/networking/" title="Networking">Networking</a></p>The "not owner" error is displayed on the client system (usually Solaris) when attempting to mount an NFS share from a server. This error may appear even though the share is correctly exported and the client system has full access. If you are getting a "permission denied" error, then this article is not for you and you should check here instead.]]></description>
		<wfw:commentRss>http://www.krazyworks.com/nfs-not-owner-error/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Forcing Linux to Reboot</title>
		<link>http://www.krazyworks.com/forcing-linux-to-reboot/</link>
		<comments>http://www.krazyworks.com/forcing-linux-to-reboot/#comments</comments>
		<pubDate>Fri, 29 Jan 2010 19:21:35 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Commands & Shells]]></category>
		<category><![CDATA[Filesystems]]></category>
		<category><![CDATA[force reboot]]></category>
		<category><![CDATA[force shutdown]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[linux reboot]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=1935</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/commands-and-shells/" title="Commands &amp; Shells">Commands &amp; Shells</a><a href="http://www.krazyworks.com/category/sysadmin/data/filesystems/" title="Filesystems">Filesystems</a></p>Until I branched out a few years ago from supporting Unix server to working with Linux clusters, I never really encountered this issue: you type "reboot", "init 0", or "shutdown" as root and... nothing happens.  Or the system starts going down but then hangs on unmounting a filesystem or unloading a module. I think this happened once to a colleague of mine who was rebooting a Solaris server, but this is a common problem with Linux.]]></description>
		<wfw:commentRss>http://www.krazyworks.com/forcing-linux-to-reboot/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>WordPress File Upload Size Limit</title>
		<link>http://www.krazyworks.com/wordpress-file-upload-size-limit/</link>
		<comments>http://www.krazyworks.com/wordpress-file-upload-size-limit/#comments</comments>
		<pubDate>Sat, 26 Dec 2009 01:24:26 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Commands & Shells]]></category>
		<category><![CDATA[Scripts]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[php.ini]]></category>
		<category><![CDATA[upload site limit]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[wordpress file upload]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=1864</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/commands-and-shells/" title="Commands &amp; Shells">Commands &amp; Shells</a><a href="http://www.krazyworks.com/category/sysadmin/scripts/" title="Scripts">Scripts</a><a href="http://www.krazyworks.com/category/sysadmin/web-design/" title="Web Design">Web Design</a></p>By default, WordPress will not allow you to upload a file larger than 2Mb. This limit is not set by WordPress itself, but by detaul PHP configuration. This configuration file is usually /etc/php.ini, but normally ...]]></description>
		<wfw:commentRss>http://www.krazyworks.com/wordpress-file-upload-size-limit/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Reboot Remote Windows Workstation</title>
		<link>http://www.krazyworks.com/reboot-remote-windows-workstation/</link>
		<comments>http://www.krazyworks.com/reboot-remote-windows-workstation/#comments</comments>
		<pubDate>Thu, 10 Dec 2009 13:53:58 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Commands & Shells]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[login]]></category>
		<category><![CDATA[RDP]]></category>
		<category><![CDATA[reboot]]></category>
		<category><![CDATA[Remote]]></category>
		<category><![CDATA[shutdown]]></category>
		<category><![CDATA[windows]]></category>
		<category><![CDATA[workstation]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=1714</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/commands-and-shells/" title="Commands &amp; Shells">Commands &amp; Shells</a><a href="http://www.krazyworks.com/category/sysadmin/networking/" title="Networking">Networking</a></p>When using RDP, sometimes the session may lock up and you may need to reboot your workstation remotely. This can be done using the &#8220;shutdown.exe&#8221; command from your local PC. First, make sure you can ...]]></description>
		<wfw:commentRss>http://www.krazyworks.com/reboot-remote-windows-workstation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Slow SSH login in SuSE Linux</title>
		<link>http://www.krazyworks.com/slow-ssh-login-in-suse-linux/</link>
		<comments>http://www.krazyworks.com/slow-ssh-login-in-suse-linux/#comments</comments>
		<pubDate>Tue, 03 Nov 2009 22:17:55 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Commands & Shells]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[broadcast]]></category>
		<category><![CDATA[configuration file]]></category>
		<category><![CDATA[hostname]]></category>
		<category><![CDATA[hosts]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[opensuse]]></category>
		<category><![CDATA[putty]]></category>
		<category><![CDATA[ssh login]]></category>
		<category><![CDATA[suse 10]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=1702</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/commands-and-shells/" title="Commands &amp; Shells">Commands &amp; Shells</a><a href="http://www.krazyworks.com/category/sysadmin/networking/" title="Networking">Networking</a></p>Starting with SuSE 10 and including both openSuSE and SLES an annoying SSH problem appeared. When you SSH to the server (via PuTTY and such) you get the &#8220;login&#8221; prompts right away, but the &#8220;password&#8221; ...]]></description>
		<wfw:commentRss>http://www.krazyworks.com/slow-ssh-login-in-suse-linux/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Shell Scripting for HPC Clusters, Part 2</title>
		<link>http://www.krazyworks.com/shell-scripting-for-hpc-clusters-part-2/</link>
		<comments>http://www.krazyworks.com/shell-scripting-for-hpc-clusters-part-2/#comments</comments>
		<pubDate>Fri, 23 Oct 2009 16:30:13 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Commands & Shells]]></category>
		<category><![CDATA[Scripts]]></category>
		<category><![CDATA[array elements]]></category>
		<category><![CDATA[bash]]></category>
		<category><![CDATA[configuration]]></category>
		<category><![CDATA[korn shell]]></category>
		<category><![CDATA[korn shell array]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[random number generator]]></category>
		<category><![CDATA[search script]]></category>
		<category><![CDATA[shell script]]></category>
		<category><![CDATA[shell variables]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=1675</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/commands-and-shells/" title="Commands &amp; Shells">Commands &amp; Shells</a><a href="http://www.krazyworks.com/category/sysadmin/scripts/" title="Scripts">Scripts</a></p>This is the second installment of a multipart guide for beginner Unix sysadmins supporting HPC clusters. You can view the first part of the guide here.
Searching, Replacing, Comparing
Try to work with a large cluster and ...]]></description>
		<wfw:commentRss>http://www.krazyworks.com/shell-scripting-for-hpc-clusters-part-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

