<?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>Linux System Admins Blog &#187; sysadmin</title>
	<atom:link href="http://linuxsysadminblog.com/category/sysadmin/feed/" rel="self" type="application/rss+xml" />
	<link>http://linuxsysadminblog.com</link>
	<description>System admins of Promet - an e-commerce, high availability Open Source web shop - share their findings</description>
	<lastBuildDate>Sat, 10 Jul 2010 01:33:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>HowTo remove a list of files</title>
		<link>http://linuxsysadminblog.com/2010/07/howto-remove-a-list-of-files/</link>
		<comments>http://linuxsysadminblog.com/2010/07/howto-remove-a-list-of-files/#comments</comments>
		<pubDate>Fri, 09 Jul 2010 21:33:28 +0000</pubDate>
		<dc:creator>marius</dc:creator>
				<category><![CDATA[CLI]]></category>
		<category><![CDATA[HowTo]]></category>
		<category><![CDATA[Tips and Tricks]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[bash]]></category>
		<category><![CDATA[tips]]></category>

		<guid isPermaLink="false">http://linuxsysadminblog.com/?p=1116</guid>
		<description><![CDATA[Here is a quick tip on how to remove a list of files. Let&#8217;s say you have the list of files inside a file called files_to_remove. Usually I would do something like this:
LIST=`cat files_to_remove`
and then
ls -al $LIST
just to check what is in the list and if it looks good.
And finally:
rm -vf $LIST
]]></description>
			<content:encoded><![CDATA[<p>Here is a quick tip on how to remove a list of files. Let&#8217;s say you have the list of files inside a file called <strong>files_to_remove</strong>. Usually I would do something like this:<br />
<code>LIST=`cat files_to_remove`</code><br />
and then<br />
<code>ls -al $LIST</code><br />
just to check what is in the list and if it looks good.</p>
<p>And finally:<br />
<code>rm -vf $LIST</code></p>
]]></content:encoded>
			<wfw:commentRss>http://linuxsysadminblog.com/2010/07/howto-remove-a-list-of-files/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google will use site performance and page load speed in SERP ranking &#8211; sysadmin SEO here we come</title>
		<link>http://linuxsysadminblog.com/2010/04/google-will-use-site-performance-and-page-load-speed-in-serp-ranking-sysadmin-seo-here-we-come/</link>
		<comments>http://linuxsysadminblog.com/2010/04/google-will-use-site-performance-and-page-load-speed-in-serp-ranking-sysadmin-seo-here-we-come/#comments</comments>
		<pubDate>Wed, 14 Apr 2010 04:48:56 +0000</pubDate>
		<dc:creator>andrew</dc:creator>
				<category><![CDATA[Performance]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[page load speed]]></category>
		<category><![CDATA[SEO]]></category>

		<guid isPermaLink="false">http://linuxsysadminblog.com/?p=1075</guid>
		<description><![CDATA[Page Load speed just became a lot more important &#8211; Google announced recently that it will use page speed in its SERP rankings.  Here is a quote that will make the SEO and marketing folks knock on sysadmin doors:
We encourage you to start looking at your site&#8217;s speed (the tools above provide a great [...]]]></description>
			<content:encoded><![CDATA[<p>Page Load speed just became a lot more important &#8211; Google announced recently that it will use <a href="http://googlewebmastercentral.blogspot.com/2010/04/using-site-speed-in-web-search-ranking.html">page speed in its SERP</a> rankings.  Here is a quote that will make the SEO and marketing folks knock on sysadmin doors:</p>
<blockquote><p>We encourage you to start looking at your site&#8217;s speed (the tools above provide a great starting point) — not only to improve your ranking in search engines, but also to improve everyone&#8217;s experience on the Internet.</p></blockquote>
<p>The post lists a number of tools everyone should be using already, such as <a href="http://developer.yahoo.com/yslow/" target="_blank">YSlow</a>, google&#8217;s own <a href="http://code.google.com/speed/page-speed/">PageSpeed</a>, <a href="http://www.webpagetest.org/">online speed waterfall diagram</a> tool and webmaster tools.  Webmaster tools recently added a beta feature which provides data about your sites speed relative to other sites on the internet.</p>
<p>Here is a sample report:</p>
<div id="attachment_1076" class="wp-caption aligncenter" style="width: 760px"><a href="http://linuxsysadminblog.com/wp-content/uploads/2010/04/chart.png"><img class="size-full wp-image-1076" title="webmaster tools page speed chart" src="http://linuxsysadminblog.com/wp-content/uploads/2010/04/chart.png" alt="google webmaster tools page load speed chart" width="750" height="150" /></a><p class="wp-caption-text">webmaster tools page speed chart</p></div>
<blockquote><p>Performance overview<br />
On average, pages in your site take 6.3 seconds to load (updated on Apr 11, 2010). This is slower than 83% of sites. These estimates are of medium accuracy (between 100 and 1000 data points). The chart below shows how your site&#8217;s average page load time has changed over the last few months. For your reference, it also shows the 20th percentile value across all sites, separating slow and fast load times.</p></blockquote>
<p>Linus System admin blog will have a series on page speed improvement.  Stay tuned!</p>
]]></content:encoded>
			<wfw:commentRss>http://linuxsysadminblog.com/2010/04/google-will-use-site-performance-and-page-load-speed-in-serp-ranking-sysadmin-seo-here-we-come/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Enable/Disable APC on virtual host level</title>
		<link>http://linuxsysadminblog.com/2010/03/enabledisable-apc-on-virtual-host-level/</link>
		<comments>http://linuxsysadminblog.com/2010/03/enabledisable-apc-on-virtual-host-level/#comments</comments>
		<pubDate>Thu, 18 Mar 2010 21:53:29 +0000</pubDate>
		<dc:creator>marius</dc:creator>
				<category><![CDATA[Performance]]></category>
		<category><![CDATA[Tips and Tricks]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[apc]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[tips]]></category>

		<guid isPermaLink="false">http://linuxsysadminblog.com/?p=1069</guid>
		<description><![CDATA[APC (Alternative PHP Cache) is a free, open, and robust framework for caching and optimizing PHP intermediate code. APC is a great tool to speed up a php driven site and I can&#8217;t even think of a big site running on a php framework without an opcode cache (other good choices are eaccelerator or xcache). [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://pecl.php.net/package/APC" target="_blank"><strong>APC</strong></a> (Alternative PHP Cache) is a free, open, and robust framework for caching and optimizing PHP intermediate code. <strong>APC</strong> is a great tool to speed up a php driven site and I can&#8217;t even think of a big site running on a php framework without an <em>opcode cache</em> (other good choices are <strong>eaccelerator</strong> or <strong>xcache</strong>). Why would not everyone want to use this? The reason why this is not enabled by default everywhere is because in certain situations it can break things. Most peoples will not see any problems, but still, if you run a server with many clients sharing the same apache service this might be a problem (as the apc module loading it is a server-wide config). This post will show how we can use APC globally and disable it for some vhosts (that might have a problem with using APC) or the reverse to just use it one a special vhost that might need this.</p>
<p>I&#8217;ll assume that you have installed apc already, if this is not the case this will probably be something as simple as running<br />
<code>pecl install apc</code><br />
or downloading the archive from pecl and running:<br />
<code>phpize; ./configure; make; make install</code></p>
<p>The APC extension needs to be enabled either in <strong>php.ini</strong> or in one included file with a line like this:<br />
<code>extension=apc.so</code><br />
there are many other parameters that apc can be fine tuned (see the official doc for more info), but without any other change, just with this line apc will be enabled on all the vhosts on the server.</p>
<p><strong>Disabling some vhosts from using APC</strong><br />
- if we want to disable APC for a particular vhost we just have to add to the vhost config or to .htaccess:<br />
<code>php_flag apc.cache_by_default Off</code></p>
<p><strong>Enabling APC only on some vhosts</strong><br />
- if we want to have APC disabled by default globally we will have in php.ini:</p>
<pre><code>extension=apc.so
[apc]
apc.cache_by_default=0 # disable by default
... other apc settings...</code></pre>
<p>and we will enable APC for the particular vhost config or using .htaccess using:<br />
<code>php_flag apc.cache_by_default On</code></p>
<p>Hopefully you found this post useful and this will give you a reason to use APC with more confidence knowing that you have the granularity to disable/enable it as needed in a shared environment.</p>
]]></content:encoded>
			<wfw:commentRss>http://linuxsysadminblog.com/2010/03/enabledisable-apc-on-virtual-host-level/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mail Relay Issue on Cpanel Server</title>
		<link>http://linuxsysadminblog.com/2010/02/mail-relay-issue-on-cpanel-server/</link>
		<comments>http://linuxsysadminblog.com/2010/02/mail-relay-issue-on-cpanel-server/#comments</comments>
		<pubDate>Tue, 16 Feb 2010 14:05:00 +0000</pubDate>
		<dc:creator>gerold</dc:creator>
				<category><![CDATA[Centos]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[hosting]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[exim]]></category>
		<category><![CDATA[relayers]]></category>

		<guid isPermaLink="false">http://linuxsysadminblog.com/?p=1050</guid>
		<description><![CDATA[I noticed lots of email being relayed on one of our shared hosting server, CentOS5 with Cpanel and running Exim, and the strange thing is that the email server (MX) for these accounts are pointing to Google (GoogleApps), and we have correct entries for localdomains and remotedomains for these account.  The relayers (&#8216;From&#8217; server/address) [...]]]></description>
			<content:encoded><![CDATA[<p>I noticed lots of email being relayed on one of our shared hosting server, CentOS5 with Cpanel and running Exim, and the strange thing is that the email server (MX) for these accounts are pointing to Google (GoogleApps), and we have correct entries for <em>localdomains</em> and <em>remotedomains</em> for these account.  The relayers (<em>&#8216;From&#8217;</em> server/address) looks like spam anyway.  From the mail logs I noticed that the relayed messages have &#8216;<em>fixed_login</em>&#8216; and key (&#8216;<em>rsa-sha1</em>&#8216;) for their authentications.</p>
<p>Since the mail server for these accounts are pointing to other servers, I deleted all the email accounts, forwarders, mailinglists, etc.  After this I&#8217;ve seen sending error/failure messages from mail logs of the said accounts  It shows &#8216;<em>fixed_login authenticator failed for hostxx&#8217; [535 Incorrect authentication data]</em>.</p>
]]></content:encoded>
			<wfw:commentRss>http://linuxsysadminblog.com/2010/02/mail-relay-issue-on-cpanel-server/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Change Squid outgoing address</title>
		<link>http://linuxsysadminblog.com/2009/10/change-squid-outgoing-address/</link>
		<comments>http://linuxsysadminblog.com/2009/10/change-squid-outgoing-address/#comments</comments>
		<pubDate>Mon, 19 Oct 2009 18:45:34 +0000</pubDate>
		<dc:creator>max</dc:creator>
				<category><![CDATA[Installation]]></category>
		<category><![CDATA[Tips and Tricks]]></category>
		<category><![CDATA[sysadmin]]></category>

		<guid isPermaLink="false">http://linuxsysadminblog.com/?p=898</guid>
		<description><![CDATA[Typically Squid caching proxy server listen and outgoing IP address are the same. Sometimes, for various reasons we want to alter the outgoing IP address. The new address must first be brought up as an interface on the squid server. In squid.conf look for tcp_outgoing_address line, uncomment it and replace the default IP value with [...]]]></description>
			<content:encoded><![CDATA[<p>Typically <a href="http://www.squid-cache.org">Squid</a> caching proxy server listen and outgoing IP address are the same. Sometimes, for various reasons we want to alter the <strong>outgoing IP</strong> address. The new address must first be brought up as an interface on the squid server. In squid.conf look for <code>tcp_outgoing_address</code> line, uncomment it and replace the default IP value with your new outgoing ip address and restart Squid. Your Squid server will still listen and accept connections on the current IP while all outbound traffic will originate from the new IP. This modification works with access ACL and detailed instructions can be found <a href="http://www.squid-cache.org/Versions/v3/3.0/cfgman/tcp_outgoing_address.html">here</a> for latest stable branch (3.0)</p>
]]></content:encoded>
			<wfw:commentRss>http://linuxsysadminblog.com/2009/10/change-squid-outgoing-address/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HowTo display PHP errors when you don&#8217;t have access to php.ini</title>
		<link>http://linuxsysadminblog.com/2009/09/howto-display-php-errors-when-you-dont-have-access-to-php-ini/</link>
		<comments>http://linuxsysadminblog.com/2009/09/howto-display-php-errors-when-you-dont-have-access-to-php-ini/#comments</comments>
		<pubDate>Tue, 15 Sep 2009 12:10:34 +0000</pubDate>
		<dc:creator>marius</dc:creator>
				<category><![CDATA[CLI]]></category>
		<category><![CDATA[Centos]]></category>
		<category><![CDATA[Debian]]></category>
		<category><![CDATA[HowTo]]></category>
		<category><![CDATA[Tips and Tricks]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[php]]></category>

		<guid isPermaLink="false">http://linuxsysadminblog.com/?p=867</guid>
		<description><![CDATA[If you are using a shared server, or just have a limited account on your company servers, you might not have access to your php configuration file php.ini (this is usually found under /etc/php.ini in rhel/centos and /etc/php5/apache2/php.ini in debian/ubuntu). Still, in many situations it might be needed to enable php errors in the browser [...]]]></description>
			<content:encoded><![CDATA[<p>If you are using a shared server, or just have a limited account on your company servers, you might <strong>not have access</strong> to your php configuration file <strong>php.ini</strong> (this is usually found under <em>/etc/php.ini</em> in rhel/centos and <em>/etc/php5/apache2/php.ini</em> in debian/ubuntu). Still, in many situations it might be needed to <strong>enable php errors</strong> in the browser so you can see what is the actual problem instead of an empty page (if the server has error reporting disabled as most production systems should have).</p>
<p>In order to enable error reporting for your php script or application include inside your code the following lines:<br />
<code>error_reporting(E_ALL);<br />
ini_set("display_errors", 1);</code><br />
and this will result in displaying in the browser any errors your application might have.</p>
<p>ps: once you are done with this and fixed the issue, don&#8217;t forget to remove the error reporting lines, as we don&#8217;t want our users/clients to see errors in the browser in case something went wrong.</p>
]]></content:encoded>
			<wfw:commentRss>http://linuxsysadminblog.com/2009/09/howto-display-php-errors-when-you-dont-have-access-to-php-ini/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>CentOS 4.8 finally released!</title>
		<link>http://linuxsysadminblog.com/2009/09/centos-4-8-finally-released/</link>
		<comments>http://linuxsysadminblog.com/2009/09/centos-4-8-finally-released/#comments</comments>
		<pubDate>Tue, 01 Sep 2009 10:03:36 +0000</pubDate>
		<dc:creator>marius</dc:creator>
				<category><![CDATA[Centos]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[sysadmin]]></category>

		<guid isPermaLink="false">http://linuxsysadminblog.com/?p=842</guid>
		<description><![CDATA[After a long development time, Centos 4.8 was finally released on the 21st August. This is a good thing that after the latest problems between the centos developers, they were able to pull this out finally and now be able to focus on the upcoming 5.4 release.
There are no major changes in this update, mostly [...]]]></description>
			<content:encoded><![CDATA[<p>After a long development time, <strong>Centos 4.8</strong> was finally <a href="http://lists.centos.org/pipermail/centos-announce/2009-August/016106.html" target="_blank">released</a> on the 21st August. This is a good thing that after the latest <a href="http://www.centos.org/modules/news/article.php?storyid=381" target="_blank">problems</a> between the centos developers, they were able to pull this out finally and now be able to focus on the upcoming 5.4 release.</p>
<p>There are no major <a href="http://www.centos.org/docs/4/4.8/release_notes/" target="_blank">changes</a> in this update, mostly <em>bug fixes and security fixes</em>, and it should be a quick and easy upgrade for most people still running the 4.x branch (you should really consider upgrading to 5.x <img src='http://linuxsysadminblog.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />  ).</p>
]]></content:encoded>
			<wfw:commentRss>http://linuxsysadminblog.com/2009/09/centos-4-8-finally-released/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using wildcards in nginx valid_referers</title>
		<link>http://linuxsysadminblog.com/2009/08/using-wildcards-in-nginx-valid_referers/</link>
		<comments>http://linuxsysadminblog.com/2009/08/using-wildcards-in-nginx-valid_referers/#comments</comments>
		<pubDate>Tue, 25 Aug 2009 11:05:25 +0000</pubDate>
		<dc:creator>marius</dc:creator>
				<category><![CDATA[HowTo]]></category>
		<category><![CDATA[Tips and Tricks]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[nginx]]></category>
		<category><![CDATA[tips]]></category>

		<guid isPermaLink="false">http://linuxsysadminblog.com/?p=833</guid>
		<description><![CDATA[This quick post will show how we can easily allow only certain http referrers see some location using nginx. This might be useful for example if you are using nginx as a static content provider and want to not allow everyone hot-linking your images and only your own sites. Doing something like this in nginx [...]]]></description>
			<content:encoded><![CDATA[<p>This quick post will show how we can easily allow only certain http referrers see some location using <a href="http://nginx.net/" target="_blank"><strong>nginx</strong></a>. This might be useful for example if you are using nginx as a static content provider and want to not allow everyone hot-linking your images and only your own sites. Doing something like this in nginx is very simple and we could start with a configuration like this (from <em>nginx.conf</em>):</p>
<pre><code>location /images {
	valid_referers   none  blocked  server_names  mydomain.com www.mydomain.com;
	if ($invalid_referer) {
		return   403;
	}
	... else serve the content
}</code></pre>
<p>This works fine in this simple case; but what if we need to list more sub-domains? like images.mydomain.com an static.mydomain.com, etc? It would be nice to be able to use a regexp for this, right? Fortunately nginx has support for this and this can be done using a valid_referers line like:<br />
<code>valid_referers   none  blocked  server_names  ~(mydomain.com)</code></p>
<p><span id="more-833"></span>And this will match all the subdomains *.mydomain.com. Going even further you might want to allow google as a referrer for you content. Still google has so many subdomains and even different domains (like google.com, google.de, etc.) For this we could add ~(google.) and have our final configuration look like this:</p>
<pre><code>location /images {
	valid_referers   none  blocked  server_names  ~(mydomain.com|google.);
	if ($invalid_referer) {
		return   403;
	}
	... else serve the content
}</code></pre>
<p>This simple example shows how powerful the configuration of nginx is and how easy it is to do things that are rather impossible with other similar softwares.</p>
]]></content:encoded>
			<wfw:commentRss>http://linuxsysadminblog.com/2009/08/using-wildcards-in-nginx-valid_referers/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Using svn+ssh with a non-standard ssh port</title>
		<link>http://linuxsysadminblog.com/2009/08/using-svnssh-with-a-non-standard-ssh-port/</link>
		<comments>http://linuxsysadminblog.com/2009/08/using-svnssh-with-a-non-standard-ssh-port/#comments</comments>
		<pubDate>Mon, 17 Aug 2009 09:25:05 +0000</pubDate>
		<dc:creator>marius</dc:creator>
				<category><![CDATA[CLI]]></category>
		<category><![CDATA[HowTo]]></category>
		<category><![CDATA[Tips and Tricks]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[ssh]]></category>
		<category><![CDATA[subversion]]></category>
		<category><![CDATA[svn]]></category>

		<guid isPermaLink="false">http://linuxsysadminblog.com/?p=829</guid>
		<description><![CDATA[Many people use subversion over ssh for a simple and secure way to work on remotely hosted svn repositories. This is normally as simple as running:
svn co svn+ssh://user@server/repo .
If the remote ssh server is not running on the default ssh port (tcp 22) then this needs a little tweaking to get it working. Normally I [...]]]></description>
			<content:encoded><![CDATA[<p>Many people use <a href="http://subversion.tigris.org/" target="_blank"><strong>subversion</strong></a> over ssh for a simple and secure way to work on remotely hosted svn repositories. This is normally as simple as running:<br />
<code>svn co svn+ssh://user@server/repo .</code></p>
<p>If the remote ssh server is <strong>not running on the default ssh port</strong> (tcp 22) then this needs a little tweaking to get it working. Normally I was expecting that adding a custom entry for the svn server in the <em>/etc/ssh/ssh_config</em> file with the appropriate port would make this work on the fly without changing the command line; or if not, adding the ssh port in &#8216;telnet like&#8217; way: <em>server:port</em> would make a difference. Still none of those worked and in order to get this working I had to dig into the subversion documentation on how we can define a special tunnel.</p>
<p>We can define a new tunnel in the svn configuration file (<strong>.subversion/config</strong>):<br />
<code>[tunnels]<br />
sshtunnel = ssh -p &lt;port&gt;</code></p>
<p>And after this we can use svn as usual but with a url like <strong>svn+sshtunnel://</strong> :<br />
<code>svn co svn+sshtunnel://user@server/repo .</code></p>
]]></content:encoded>
			<wfw:commentRss>http://linuxsysadminblog.com/2009/08/using-svnssh-with-a-non-standard-ssh-port/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>System Admin Day &#8211; July 31st</title>
		<link>http://linuxsysadminblog.com/2009/07/july-31st-system-admin-day/</link>
		<comments>http://linuxsysadminblog.com/2009/07/july-31st-system-admin-day/#comments</comments>
		<pubDate>Thu, 30 Jul 2009 18:41:14 +0000</pubDate>
		<dc:creator>andrew</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[sysadmin]]></category>

		<guid isPermaLink="false">http://linuxsysadminblog.com/?p=822</guid>
		<description><![CDATA[We will celebrate the Linux System Administrator Appriciation day tomorrow.  Yes, there is such a thing, if its in wikipedia (wiki system administrator appreciation Day), than it must be true!
See what its all about here:
System Administrator Appreciation Day, also known as Sysadmin Day, SysAdminDay or SAAD, was created by system administrator Ted Kekatos. Kekatos was inspired to create [...]]]></description>
			<content:encoded><![CDATA[<p>We will celebrate the Linux System Administrator Appriciation day tomorrow.  Yes, there is such a thing, if its in wikipedia (<a href="http://en.wikipedia.org/wiki/System_Administrator_Appreciation_Day">wiki system administrator appreciation Day</a>), than it must be true!</p>
<p>See what its all about here:</p>
<blockquote><p><strong>System Administrator Appreciation Day</strong>, also known as <strong>Sysadmin Day</strong>, <strong>SysAdminDay</strong> or <strong>SAAD</strong>, was created by <a style="text-decoration: none; color: #002bb8; background-image: none; background-repeat: initial; background-attachment: initial; -webkit-background-clip: initial; -webkit-background-origin: initial; background-color: initial; background-position: initial initial;" title="System administrator" href="http://en.wikipedia.org/wiki/System_administrator">system administrator</a> Ted Kekatos. Kekatos was inspired to create the special day by a <a style="text-decoration: none; color: #002bb8; background-image: none; background-repeat: initial; background-attachment: initial; -webkit-background-clip: initial; -webkit-background-origin: initial; background-color: initial; background-position: initial initial;" title="Hewlett-Packard" href="http://en.wikipedia.org/wiki/Hewlett-Packard">Hewlett-Packard</a> magazine advertisement in which a system administrator is presented with flowers and fruit-baskets by grateful co-workers as thanks for installing new printers.</p></blockquote>
<p style="text-align: left;">
<p>Here is one of our own getting some appreciation from our colleagues.</p>
<div id="attachment_823" class="wp-caption alignleft" style="width: 310px"><img class="size-medium wp-image-823" title="LinuxSystemAdmin-gets-love-from-ladies" src="http://linuxsysadminblog.com/wp-content/uploads/2009/07/LinuxSystemAdmin-gets-love-from-ladies-300x225.jpg" alt="Max, our gets nominated as a favorite linux system administrator by some of his office fans" width="300" height="225" /><p class="wp-caption-text">Max, our gets nominated as a favorite linux system administrator by some of his office fans</p></div>
<p>So don&#8217;t forget to buy your system administrator a coffee, beer, donut, or whatever he prefers, and dont ask any stupid questions tomorrow.</p>
<p><strong>The system administrator song</strong></p>
<p><object width="480" height="392" data="http://flash.revver.com/player/1.0/player.swf?mediaId=5580&#038;affiliate=1722" type="application/x-shockwave-flash" id="revver558012489788006752409"><param name="Movie" value="http://flash.revver.com/player/1.0/player.swf?mediaId=5580&#038;affiliate=1722"></param><param name="FlashVars" value="allowFullScreen=true"></param><param name="AllowFullScreen" value="true"></param><param name="AllowScriptAccess" value="always"></param><embed type="application/x-shockwave-flash" src="http://flash.revver.com/player/1.0/player.swf?mediaId=5580&#038;affiliate=1722" pluginspage="http://www.macromedia.com/go/getflashplayer" allowScriptAccess="always" flashvars="allowFullScreen=true" allowfullscreen="true" height="392" width="480"></embed></object></p>
<p>And here is a link to another System administrator song from the UK</p>
<p>http://www.ukuug.org/sysadminday/</p>
]]></content:encoded>
			<wfw:commentRss>http://linuxsysadminblog.com/2009/07/july-31st-system-admin-day/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
