<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Administration on System Overlord</title><link>https://systemoverlord.com/tags/administration.html</link><description>Recent content in Administration on System Overlord</description><generator>Hugo</generator><language>en-us</language><managingEditor>david@systemoverlord.com (David Tomaschik)</managingEditor><webMaster>david@systemoverlord.com (David Tomaschik)</webMaster><lastBuildDate>Sat, 05 Mar 2011 23:50:32 +0000</lastBuildDate><atom:link href="https://systemoverlord.com/tags/administration/index.xml" rel="self" type="application/rss+xml"/><item><title>Memo to Self when Moving Databases</title><link>https://systemoverlord.com/2011/03/05/memo-to-self-when-moving-databases/</link><pubDate>Sat, 05 Mar 2011 23:50:32 +0000</pubDate><author>david@systemoverlord.com (David Tomaschik)</author><guid>https://systemoverlord.com/2011/03/05/memo-to-self-when-moving-databases/</guid><description>&lt;p&gt;As a memo to myself, and in case others aren't aware of this:&lt;/p&gt;
&lt;p&gt;If you move the entirety of a mysql server (e.g., all databases, especially the "mysql" database) to a new Debian-based (Debian, Ubuntu, etc.) server, you need to make sure the debian-sys-maint user is created or updated.&lt;/p&gt;
&lt;p&gt;If moving from a non-Debian-ish environment, try: &lt;/p&gt;
&lt;pre&gt;GRANT ALL PRIVILEGES ON *.* TO 'debian-sys-maint'@'localhost' IDENTIFIED BY '--password--' WITH GRANT OPTION;&lt;/pre&gt;&lt;p&gt; where "--password--" comes from /etc/mysql/debian.cnf.&lt;/p&gt;</description></item><item><title>apc.stat=0 and Updating Software</title><link>https://systemoverlord.com/2011/02/08/apcstat0-and-updating-software/</link><pubDate>Tue, 08 Feb 2011 04:36:41 +0000</pubDate><author>david@systemoverlord.com (David Tomaschik)</author><guid>https://systemoverlord.com/2011/02/08/apcstat0-and-updating-software/</guid><description>&lt;p&gt;When you're running APC on PHP and you have apc.stat=0, it's sometimes easy to forget that when you update software (WordPress) the &lt;strong&gt;code running on your server remains unchanged until you flush the APC cache.&lt;/strong&gt; So, when you go to update WordPress to 3.0.5, you should flush your APC cache after running the update.  If you don't, you'll be very confused when WordPress repeatedly tells you to upgrade to the version you just installed!&lt;/p&gt;</description></item><item><title>Welcome to Nginx!</title><link>https://systemoverlord.com/2011/01/23/welcome-to-nginx/</link><pubDate>Sun, 23 Jan 2011 17:49:21 +0000</pubDate><author>david@systemoverlord.com (David Tomaschik)</author><guid>https://systemoverlord.com/2011/01/23/welcome-to-nginx/</guid><description>&lt;p&gt;If you're reading this, it's thanks to Nginx.  As of about midnight last night, all content on SystemOverlord.com is being served up by Nginx.  I did this for two reasons: Nginx has a much smaller memory profile than Apache, which is important when running on a 512MB VPS, and Nginx's preferred PHP path is through a FastCGI interface, which allows me to run separate PHP FastCGIs under different users for each application on my server.  Privilege separation for different webapps has always been a big thing security-wise, and I'm glad I was able to get it going with a minimum of fuss.  &lt;a href="http://wordpress.org"&gt;Wordpress&lt;/a&gt;, &lt;a href="http://nginx.org"&gt;Nginx&lt;/a&gt;, &lt;a href="http://mysql.com"&gt;MySQL&lt;/a&gt;, and &lt;a href="http://ubuntu.com"&gt;Ubuntu Server&lt;/a&gt; powered, all on a &lt;a href="http://www.linode.com/?r=680a893e24df3597d32f58cd41930e969027dc06"&gt;Linode VPS&lt;/a&gt;!&lt;/p&gt;</description></item><item><title>IPv6: On my Linode, and at Home</title><link>https://systemoverlord.com/2011/01/21/ipv6-on-my-linode-and-at-home/</link><pubDate>Fri, 21 Jan 2011 02:07:32 +0000</pubDate><author>david@systemoverlord.com (David Tomaschik)</author><guid>https://systemoverlord.com/2011/01/21/ipv6-on-my-linode-and-at-home/</guid><description>&lt;p&gt;Hurricane Electric, ARIN, and others, &lt;a href="http://ipv6.he.net/statistics/"&gt;report&lt;/a&gt; that we may be as close as 12 days to exhaustion of the main IPv4 pool.  Accordingly, I decided it was time to get both my VPS and my home network IPv6-ready.  It wasn't as painful as I feared, though doing it in DD-WRT is a bigger pain than it should be.  If I had an OpenWRT router, it looks like it would be easier.&lt;/p&gt;</description></item></channel></rss>