<?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; Data</title>
	<atom:link href="http://www.krazyworks.com/category/sysadmin/data/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.krazyworks.com</link>
	<description>Networking, Systems Design, and Disaster Recovery</description>
	<lastBuildDate>Wed, 01 Feb 2012 05:53:56 +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>Adding LUNs to VXVM on Linux</title>
		<link>http://www.krazyworks.com/adding-luns-to-vxvm-on-linux/</link>
		<comments>http://www.krazyworks.com/adding-luns-to-vxvm-on-linux/#comments</comments>
		<pubDate>Tue, 06 Sep 2011 18:03:30 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Disks and Volumes]]></category>
		<category><![CDATA[Featured]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=2477</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/data/disks-and-volumes/" title="Disks and Volumes">Disks and Volumes</a><a href="http://www.krazyworks.com/category/featured/" title="Featured">Featured</a></p>The following is a brief overview of the process for adding LUNs to VXVM under Linux. In our example we have an RHEL 5 server with existing LUNs and VXVM volume groups. Two new LUNs with multipathing were allocated from SAN and need to be added to the system to grow one of the volumes and the corresponding filesystem.]]></description>
		<wfw:commentRss>http://www.krazyworks.com/adding-luns-to-vxvm-on-linux/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Facebook Security for the Lazy</title>
		<link>http://www.krazyworks.com/facebook-security-for-the-lazy/</link>
		<comments>http://www.krazyworks.com/facebook-security-for-the-lazy/#comments</comments>
		<pubDate>Thu, 28 Apr 2011 06:36:19 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Featured]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=2321</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/featured/" title="Featured">Featured</a><a href="http://www.krazyworks.com/category/sysadmin/data/security/" title="Security">Security</a></p>Every time you use Facebook, you probably have a nagging feeling in the back of your head that someone other than your friends is reading your posts. You should trust that feeling. At the same time, keep in mind that Facebook is a tool designed primarily for sharing personal information with large groups of people you barely know. Facebook is not your personal diary or a substitute for SMS.  You just need to assume that everything you post on Facebook inevitably will end up in the hands of someone you don't like very much. And then you proceed based on that assumption.]]></description>
		<wfw:commentRss>http://www.krazyworks.com/facebook-security-for-the-lazy/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Don&#8217;t Be Afraid to Reboot Unix Servers</title>
		<link>http://www.krazyworks.com/dont-be-afraid-to-reboot-unix-servers/</link>
		<comments>http://www.krazyworks.com/dont-be-afraid-to-reboot-unix-servers/#comments</comments>
		<pubDate>Tue, 22 Feb 2011 00:11:26 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Disaster Recovery]]></category>
		<category><![CDATA[Featured]]></category>
		<category><![CDATA[kernel upgrade]]></category>
		<category><![CDATA[memory leak]]></category>
		<category><![CDATA[reboot]]></category>
		<category><![CDATA[stale NFS]]></category>
		<category><![CDATA[troubleshooting]]></category>
		<category><![CDATA[Unix server]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=2275</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/data/disaster-recovery/" title="Disaster Recovery">Disaster Recovery</a><a href="http://www.krazyworks.com/category/featured/" title="Featured">Featured</a></p>Reboot your Unix servers after making any major changes to the production environment. Should an unexpected problem come up, it will be easier to deal with it when everything is still fresh in your mind and not six months down the road, when you have to do a reboot to replace a failed system board and suddenly discover that some application wouldn't load, by which time you forgot all about this application and have to start with the first page of the admin guide.]]></description>
		<wfw:commentRss>http://www.krazyworks.com/dont-be-afraid-to-reboot-unix-servers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Windows 7 Black Screen After Booting</title>
		<link>http://www.krazyworks.com/windows-7-black-screen-after-booting/</link>
		<comments>http://www.krazyworks.com/windows-7-black-screen-after-booting/#comments</comments>
		<pubDate>Tue, 05 Oct 2010 08:07:37 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Disaster Recovery]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[Samba]]></category>
		<category><![CDATA[black]]></category>
		<category><![CDATA[death]]></category>
		<category><![CDATA[drive]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[screen]]></category>
		<category><![CDATA[windows 7]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=2113</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/data/disaster-recovery/" title="Disaster Recovery">Disaster Recovery</a><a href="http://www.krazyworks.com/category/sysadmin/networking/" title="Networking">Networking</a><a href="http://www.krazyworks.com/category/sysadmin/applications/samba/" title="Samba">Samba</a></p>I had to power-cycle my Windows 7 64-bit laptop. The bootup sequence looked normal and reached a point where I could see the black screen with the mouse cursor. After this stage my desktop would usually appears, but not this time. I could move the mouse and I could even establish a remote desktop connection to my laptop. But I could not log in. Every time it would reach the same point - the black screen with the mouse cursor - and it would stop.]]></description>
		<wfw:commentRss>http://www.krazyworks.com/windows-7-black-screen-after-booting/feed/</wfw:commentRss>
		<slash:comments>3</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>How to Really Kill Computer Viruses</title>
		<link>http://www.krazyworks.com/how-to-really-kill-computer-viruses/</link>
		<comments>http://www.krazyworks.com/how-to-really-kill-computer-viruses/#comments</comments>
		<pubDate>Sun, 21 Feb 2010 10:34:20 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Applications]]></category>
		<category><![CDATA[Disaster Recovery]]></category>
		<category><![CDATA[bit]]></category>
		<category><![CDATA[boot]]></category>
		<category><![CDATA[computer]]></category>
		<category><![CDATA[Configure]]></category>
		<category><![CDATA[Copy]]></category>
		<category><![CDATA[CREATE]]></category>
		<category><![CDATA[Data]]></category>
		<category><![CDATA[destination]]></category>
		<category><![CDATA[disk]]></category>
		<category><![CDATA[DNS]]></category>
		<category><![CDATA[drive]]></category>
		<category><![CDATA[example]]></category>
		<category><![CDATA[file]]></category>
		<category><![CDATA[Files]]></category>
		<category><![CDATA[filesystem]]></category>
		<category><![CDATA[find]]></category>
		<category><![CDATA[format]]></category>
		<category><![CDATA[hard drives]]></category>
		<category><![CDATA[home]]></category>
		<category><![CDATA[ini]]></category>
		<category><![CDATA[iso]]></category>
		<category><![CDATA[iso file]]></category>
		<category><![CDATA[iso image]]></category>
		<category><![CDATA[iso images]]></category>
		<category><![CDATA[Knoppix]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[memory]]></category>
		<category><![CDATA[more]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[reboot]]></category>
		<category><![CDATA[root]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[source]]></category>
		<category><![CDATA[system disk]]></category>
		<category><![CDATA[TABLE]]></category>
		<category><![CDATA[tar]]></category>
		<category><![CDATA[test]]></category>
		<category><![CDATA[update]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=1941</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/applications/" title="Applications">Applications</a><a href="http://www.krazyworks.com/category/sysadmin/data/disaster-recovery/" title="Disaster Recovery">Disaster Recovery</a></p>How do you know if your computer has a virus? Is it connected to the Internet? Then it has a virus. Many computer viruses and other malicious applications are very resilient and will actively resist any attempts to deactivate and remove them. Some viruses can even delete your antivirus application or prevent it from working properly. Many viruses cannot be effectively removed once they are loaded in memory and active.]]></description>
		<wfw:commentRss>http://www.krazyworks.com/how-to-really-kill-computer-viruses/feed/</wfw:commentRss>
		<slash:comments>3</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>Upgrading from Vista to Windows 7</title>
		<link>http://www.krazyworks.com/upgrading-from-vista-to-windows-7/</link>
		<comments>http://www.krazyworks.com/upgrading-from-vista-to-windows-7/#comments</comments>
		<pubDate>Thu, 28 Jan 2010 02:45:24 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Applications]]></category>
		<category><![CDATA[Backups]]></category>
		<category><![CDATA[Disks and Volumes]]></category>
		<category><![CDATA[64-bit]]></category>
		<category><![CDATA[errors]]></category>
		<category><![CDATA[problems]]></category>
		<category><![CDATA[slow]]></category>
		<category><![CDATA[upgrade]]></category>
		<category><![CDATA[upgrade failed]]></category>
		<category><![CDATA[windows 7]]></category>
		<category><![CDATA[windows vista]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=1922</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/applications/" title="Applications">Applications</a><a href="http://www.krazyworks.com/category/sysadmin/data/backups/" title="Backups">Backups</a><a href="http://www.krazyworks.com/category/sysadmin/data/disks-and-volumes/" title="Disks and Volumes">Disks and Volumes</a></p>Recently I upgraded a client's Vista computer (Toshiba Qosmio, 4Gb, Intel Core Duo P7350, 7200-RPM 200-Gb disk) from Vista Ultimate 64-bit to Windows 7 Ultimate 64-bit. Being a Unix sysadmin this is not something I usually do. How did the experience compare to upgrading HP-UX, Solaris or SLES? In a nutshell: I'd rather walk around all day in wet underwear than attempt to upgrade Vista ever again. ]]></description>
		<wfw:commentRss>http://www.krazyworks.com/upgrading-from-vista-to-windows-7/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>NetBackup Command Guide</title>
		<link>http://www.krazyworks.com/netbackup-command-guide/</link>
		<comments>http://www.krazyworks.com/netbackup-command-guide/#comments</comments>
		<pubDate>Sun, 27 Dec 2009 23:17:07 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Backups]]></category>
		<category><![CDATA[Veritas]]></category>
		<category><![CDATA[cheatsheet]]></category>
		<category><![CDATA[netbackup]]></category>
		<category><![CDATA[netbackup commands]]></category>
		<category><![CDATA[netbackup troubleshooting]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=816</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/data/backups/" title="Backups">Backups</a><a href="http://www.krazyworks.com/category/sysadmin/applications/veritas/" title="Veritas">Veritas</a></p>NetBackup is an enterprise-level distributed backup and recovery application. The environment consists of the master server, media server, storage library, networking hardware, and client agents. NetBackup supports a wide variety of Unix, Linux, VMS, and Windows systems. The original backup solution was developed by Control Data Corp., later acquired by Openvision, which gave the product its "NetBackup" name. NetBackup was then bought by Veritas and is currently owned and supported (poorly) by Symantec.]]></description>
		<wfw:commentRss>http://www.krazyworks.com/netbackup-command-guide/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Copying Data: Are We There Yet?</title>
		<link>http://www.krazyworks.com/copying-data-are-we-there-yet/</link>
		<comments>http://www.krazyworks.com/copying-data-are-we-there-yet/#comments</comments>
		<pubDate>Sun, 27 Dec 2009 23:12:12 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Backups]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[Veritas]]></category>
		<category><![CDATA[backup]]></category>
		<category><![CDATA[Bonnie]]></category>
		<category><![CDATA[cluster]]></category>
		<category><![CDATA[command]]></category>
		<category><![CDATA[CPU]]></category>
		<category><![CDATA[Data]]></category>
		<category><![CDATA[disk]]></category>
		<category><![CDATA[drive]]></category>
		<category><![CDATA[filesystem]]></category>
		<category><![CDATA[FTP]]></category>
		<category><![CDATA[hard drives]]></category>
		<category><![CDATA[interface]]></category>
		<category><![CDATA[Monitoring]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[NFS]]></category>
		<category><![CDATA[partition]]></category>
		<category><![CDATA[RAM]]></category>
		<category><![CDATA[sequential input]]></category>
		<category><![CDATA[storage system]]></category>
		<category><![CDATA[stress]]></category>
		<category><![CDATA[tar]]></category>
		<category><![CDATA[test]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=898</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/data/backups/" title="Backups">Backups</a><a href="http://www.krazyworks.com/category/sysadmin/networking/" title="Networking">Networking</a><a href="http://www.krazyworks.com/category/sysadmin/monitoring/performance/" title="Performance">Performance</a><a href="http://www.krazyworks.com/category/sysadmin/applications/veritas/" title="Veritas">Veritas</a></p>I am sure this will sound familiar: you are copying a large amount of data - either locally or over the network - and you are wondering how long it will take and if there is a way to make things go faster.You may be surprised, but it does matter what type of files you are copying: 1Gb-worth of many small files will take considerably longer to copy than two 500Mb files. The hardware you are using is an important consideration, but it's not the only factor limiting data transfer speed.]]></description>
		<wfw:commentRss>http://www.krazyworks.com/copying-data-are-we-there-yet/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Testing Filesystem Performance with Bonnie++</title>
		<link>http://www.krazyworks.com/testing-filesystem-performance-with-bonnie/</link>
		<comments>http://www.krazyworks.com/testing-filesystem-performance-with-bonnie/#comments</comments>
		<pubDate>Fri, 10 Jul 2009 20:33:51 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Disks and Volumes]]></category>
		<category><![CDATA[Filesystems]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[benchmark utility]]></category>
		<category><![CDATA[benchmarking tools]]></category>
		<category><![CDATA[Bonnie]]></category>
		<category><![CDATA[hard drives]]></category>
		<category><![CDATA[sequential input]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=1376</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/data/disks-and-volumes/" title="Disks and Volumes">Disks and Volumes</a><a href="http://www.krazyworks.com/category/sysadmin/data/filesystems/" title="Filesystems">Filesystems</a><a href="http://www.krazyworks.com/category/sysadmin/monitoring/performance/" title="Performance">Performance</a></p>Bonnie++ is a benchmark utility designed to test performance of hard drives and filesystems by simulating various types of disk I/O. Bonnie++ may be used to test local disks as well as network-mounted filesystems. It ...]]></description>
		<wfw:commentRss>http://www.krazyworks.com/testing-filesystem-performance-with-bonnie/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Numeric File Permissions in Unix</title>
		<link>http://www.krazyworks.com/numeric-file-permissions-in-unix/</link>
		<comments>http://www.krazyworks.com/numeric-file-permissions-in-unix/#comments</comments>
		<pubDate>Sat, 27 Jun 2009 23:50:44 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Commands & Shells]]></category>
		<category><![CDATA[Files]]></category>
		<category><![CDATA[chmod]]></category>
		<category><![CDATA[exec]]></category>
		<category><![CDATA[Numeric]]></category>
		<category><![CDATA[permission]]></category>
		<category><![CDATA[Permissions]]></category>
		<category><![CDATA[unix]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=1295</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/files/" title="Files">Files</a></p>Suppose you are working with a Web server and your task is to make sure that no files or directories have permissions &#8220;777&#8243;. It would be easy to just recursively change permissions for all files ...]]></description>
		<wfw:commentRss>http://www.krazyworks.com/numeric-file-permissions-in-unix/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Partitioning System Disk</title>
		<link>http://www.krazyworks.com/partitioning-system-disk/</link>
		<comments>http://www.krazyworks.com/partitioning-system-disk/#comments</comments>
		<pubDate>Fri, 25 Jul 2008 00:25:03 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Disks and Volumes]]></category>
		<category><![CDATA[memory]]></category>
		<category><![CDATA[partitioning]]></category>
		<category><![CDATA[system disk]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=829</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/data/disks-and-volumes/" title="Disks and Volumes">Disks and Volumes</a></p>When performing a new Unix OS installation you are usually presented with a choice of accepting the default partitioning layout or going into advanced settings and defining your own partitions. The default layout will normally ...]]></description>
		<wfw:commentRss>http://www.krazyworks.com/partitioning-system-disk/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Linksys WAP54G Secure Configuration</title>
		<link>http://www.krazyworks.com/linksys-wap54g-secure-configuration/</link>
		<comments>http://www.krazyworks.com/linksys-wap54g-secure-configuration/#comments</comments>
		<pubDate>Wed, 11 Jun 2008 17:09:26 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[Wireless]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[wireless security]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=801</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/data/security/" title="Security">Security</a><a href="http://www.krazyworks.com/category/sysadmin/networking/wireless/" title="Wireless">Wireless</a></p>Below are some basic steps to secure a wireless access point (WAP). The screenshots are for Linksys WAP54G v. 3.04, however, the same steps will apply to wireless access points from other manufacturers. Understand this: ...]]></description>
		<wfw:commentRss>http://www.krazyworks.com/linksys-wap54g-secure-configuration/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Dealing With Disk Hogs</title>
		<link>http://www.krazyworks.com/dealing-with-disk-hogs/</link>
		<comments>http://www.krazyworks.com/dealing-with-disk-hogs/#comments</comments>
		<pubDate>Sun, 01 Jun 2008 21:49:29 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Commands & Shells]]></category>
		<category><![CDATA[Files]]></category>
		<category><![CDATA[disk hogs]]></category>
		<category><![CDATA[disk space utilization]]></category>
		<category><![CDATA[find large files]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=773</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/files/" title="Files">Files</a></p>Some users and application developers believe that any free disk space on the server belongs to them. Suddenly you get an email alert saying that a server &#8220;xyz&#8221; ran out of disk space in /home. ...]]></description>
		<wfw:commentRss>http://www.krazyworks.com/dealing-with-disk-hogs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tips on dealing with the Bagle rootkit</title>
		<link>http://www.krazyworks.com/tips-on-dealing-with-the-bagle-rootkit/</link>
		<comments>http://www.krazyworks.com/tips-on-dealing-with-the-bagle-rootkit/#comments</comments>
		<pubDate>Mon, 26 May 2008 21:51:00 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Disaster Recovery]]></category>
		<category><![CDATA[anti-virus]]></category>
		<category><![CDATA[bagle rootkit]]></category>
		<category><![CDATA[bagle virus]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=759</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/data/disaster-recovery/" title="Disaster Recovery">Disaster Recovery</a></p>Normally I don&#8217;t concern myself with Windows- related matters. However, the infamous Bagle rootkit and its numerous variations deserve some attention even from Unix sysadmins. Bagle annoyed me and my customers long enough. Essentially, Bagle ...]]></description>
		<wfw:commentRss>http://www.krazyworks.com/tips-on-dealing-with-the-bagle-rootkit/feed/</wfw:commentRss>
		<slash:comments>15</slash:comments>
		</item>
		<item>
		<title>VxVM Recovery Cheatsheet for Solaris</title>
		<link>http://www.krazyworks.com/vxvm-recovery-cheatsheet-for-solaris/</link>
		<comments>http://www.krazyworks.com/vxvm-recovery-cheatsheet-for-solaris/#comments</comments>
		<pubDate>Thu, 15 May 2008 22:22:36 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Disks and Volumes]]></category>
		<category><![CDATA[Veritas]]></category>
		<category><![CDATA[cheatsheet]]></category>
		<category><![CDATA[recovery]]></category>
		<category><![CDATA[volume manager]]></category>
		<category><![CDATA[vxvm]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=746</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/data/disks-and-volumes/" title="Disks and Volumes">Disks and Volumes</a><a href="http://www.krazyworks.com/category/sysadmin/applications/veritas/" title="Veritas">Veritas</a></p>This is a quick-and-dirty guide to recovering VxVM volumes and filesystems on a Solaris server. These instructions are not intended to be an in-depth troubleshooting guide for the Veritas Volume Manager. This is just something ...]]></description>
		<wfw:commentRss>http://www.krazyworks.com/vxvm-recovery-cheatsheet-for-solaris/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Highly redundant array configuration</title>
		<link>http://www.krazyworks.com/highly-redundant-array-configuration/</link>
		<comments>http://www.krazyworks.com/highly-redundant-array-configuration/#comments</comments>
		<pubDate>Thu, 08 May 2008 19:58:03 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Disks and Volumes]]></category>
		<category><![CDATA[Featured]]></category>
		<category><![CDATA[application availability]]></category>
		<category><![CDATA[critical applications]]></category>
		<category><![CDATA[quality storage]]></category>
		<category><![CDATA[redundant storage]]></category>
		<category><![CDATA[storage arrays]]></category>
		<category><![CDATA[storage hardware]]></category>
		<category><![CDATA[storage system]]></category>

		<guid isPermaLink="false">http://www.krazyworks.com/?p=713</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/data/disks-and-volumes/" title="Disks and Volumes">Disks and Volumes</a><a href="http://www.krazyworks.com/category/featured/" title="Featured">Featured</a></p>The cost of storage arrays is falling along with the quality of their manufacture. To quote Lev Andropov from the &#8220;Armageddon&#8221;: &#8220;Components. American components, Russian Components, ALL MADE IN TAIWAN!&#8221; What in the nineties used ...]]></description>
		<wfw:commentRss>http://www.krazyworks.com/highly-redundant-array-configuration/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Dealing with ReiserFS bad blocks</title>
		<link>http://www.krazyworks.com/dealing-with-reiserfs-bad-blocks/</link>
		<comments>http://www.krazyworks.com/dealing-with-reiserfs-bad-blocks/#comments</comments>
		<pubDate>Mon, 24 Mar 2008 23:42:14 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Filesystems]]></category>
		<category><![CDATA[bad blocks]]></category>
		<category><![CDATA[badblocksfile]]></category>
		<category><![CDATA[blocksize]]></category>
		<category><![CDATA[filesystem]]></category>
		<category><![CDATA[Knoppix]]></category>
		<category><![CDATA[ReiserFS]]></category>

		<guid isPermaLink="false">http://www.comradegeneral.com/SysAdmin/?p=141</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/data/filesystems/" title="Filesystems">Filesystems</a></p>The following is a procedure for recovering a ReiserFS filesystem with bad blocks. If this is a system FS and cannot be unmounted, the box needs to be booted from the latest version of Knoppix ...]]></description>
		<wfw:commentRss>http://www.krazyworks.com/dealing-with-reiserfs-bad-blocks/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ReiserFS Filesystem Recovery</title>
		<link>http://www.krazyworks.com/reiserfs-filesystem-recovery/</link>
		<comments>http://www.krazyworks.com/reiserfs-filesystem-recovery/#comments</comments>
		<pubDate>Fri, 21 Mar 2008 20:55:45 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Disks and Volumes]]></category>
		<category><![CDATA[filesystem]]></category>
		<category><![CDATA[inode]]></category>
		<category><![CDATA[recovery]]></category>
		<category><![CDATA[ReiserFS]]></category>
		<category><![CDATA[superblock]]></category>

		<guid isPermaLink="false">http://www.comradegeneral.com/SysAdmin/?p=140</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/data/disks-and-volumes/" title="Disks and Volumes">Disks and Volumes</a></p>The this is a description of a method for recovering ReiserFS filesystems from failed disks with bad blocks, when other recovery methods (reiserfsck) will not work. For this example, the failed server is called node1 ...]]></description>
		<wfw:commentRss>http://www.krazyworks.com/reiserfs-filesystem-recovery/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Distributed password cracking with Medussa</title>
		<link>http://www.krazyworks.com/distributed-password-cracking-with-medussa/</link>
		<comments>http://www.krazyworks.com/distributed-password-cracking-with-medussa/#comments</comments>
		<pubDate>Wed, 10 May 2006 19:43:29 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Applications]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[awk print]]></category>
		<category><![CDATA[decryption]]></category>
		<category><![CDATA[medussa]]></category>
		<category><![CDATA[root password]]></category>
		<category><![CDATA[tentacle]]></category>

		<guid isPermaLink="false">http://www.comradegeneral.com/SysAdmin/?p=103</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/applications/" title="Applications">Applications</a><a href="http://www.krazyworks.com/category/sysadmin/data/security/" title="Security">Security</a></p>Medussa is a password cracking application that supports distributed processing. One node acts as the Medussa server and the rest of the nodes are running the client application. The server node, in addition to running ...]]></description>
		<wfw:commentRss>http://www.krazyworks.com/distributed-password-cracking-with-medussa/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mountpoint permission problem in Solaris</title>
		<link>http://www.krazyworks.com/mountpoint-permission-problem-in-solaris/</link>
		<comments>http://www.krazyworks.com/mountpoint-permission-problem-in-solaris/#comments</comments>
		<pubDate>Thu, 04 May 2006 23:45:43 +0000</pubDate>
		<dc:creator>Igor</dc:creator>
				<category><![CDATA[Filesystems]]></category>
		<category><![CDATA[chmod]]></category>
		<category><![CDATA[filesystem]]></category>
		<category><![CDATA[mountpoint]]></category>
		<category><![CDATA[NFS]]></category>
		<category><![CDATA[permission]]></category>
		<category><![CDATA[problem]]></category>
		<category><![CDATA[solaris]]></category>
		<category><![CDATA[umount]]></category>
		<category><![CDATA[unshare]]></category>

		<guid isPermaLink="false">http://www.comradegeneral.com/SysAdmin/?p=102</guid>
		<description><![CDATA[<p>Posted in <a href="http://www.krazyworks.com/category/sysadmin/data/filesystems/" title="Filesystems">Filesystems</a></p>The following condition was originally discovered in OpenSolaris 11 (Bug ID: 4697677).  This problem occurs when you do mkdir -m 700 on a mountpoint before mounting it. This superceeds whatever permissions you might give ...]]></description>
		<wfw:commentRss>http://www.krazyworks.com/mountpoint-permission-problem-in-solaris/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

