<?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>MrBrown blob &#187; Distro</title>
	<atom:link href="http://charles.lescampeurs.org/category/distro/feed" rel="self" type="application/rss+xml" />
	<link>http://charles.lescampeurs.org</link>
	<description>random bits.</description>
	<lastBuildDate>Sat, 10 Apr 2010 09:02:57 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Nginx and worker_connections are more than open file resource limit warning</title>
		<link>http://charles.lescampeurs.org/2009/03/09/nginx-and-worker_connections-are-more-than-open-file-resource-limit-warning</link>
		<comments>http://charles.lescampeurs.org/2009/03/09/nginx-and-worker_connections-are-more-than-open-file-resource-limit-warning#comments</comments>
		<pubDate>Mon, 09 Mar 2009 20:30:26 +0000</pubDate>
		<dc:creator>CharlyBr</dc:creator>
				<category><![CDATA[Distro]]></category>
		<category><![CDATA[http]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[nginx]]></category>
		<category><![CDATA[ulimit]]></category>

		<guid isPermaLink="false">http://charles.lescampeurs.org/?p=160</guid>
		<description><![CDATA[If you encounter this warning message under Linux: 2009/03/09 21:23:19 [warn] 26827#0: 4096 worker_connections are more than open file resource limit: 1024 A solution is to use the command ulimit in nginx start script, just before lunching nginx: [...] ulimit  -n 65536 [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fcharles.lescampeurs.org%2F2009%2F03%2F09%2Fnginx-and-worker_connections-are-more-than-open-file-resource-limit-warning"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fcharles.lescampeurs.org%2F2009%2F03%2F09%2Fnginx-and-worker_connections-are-more-than-open-file-resource-limit-warning&amp;style=normal" height="61" width="50" /><br />
			</a>
		</div>
<p>If you encounter this warning message under Linux:</p>
<pre>2009/03/09 21:23:19 [warn] 26827#0: 4096 worker_connections are more than open file resource limit: 1024</pre>
<p>A solution is to use the command ulimit in nginx start script, just before lunching nginx:</p>
<pre>[...]
ulimit  -n 65536
[...]</pre>
]]></content:encoded>
			<wfw:commentRss>http://charles.lescampeurs.org/2009/03/09/nginx-and-worker_connections-are-more-than-open-file-resource-limit-warning/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Debian Lenny and perl locales warning messages</title>
		<link>http://charles.lescampeurs.org/2009/02/24/debian-lenny-and-perl-locales-warning-messages</link>
		<comments>http://charles.lescampeurs.org/2009/02/24/debian-lenny-and-perl-locales-warning-messages#comments</comments>
		<pubDate>Tue, 24 Feb 2009 09:59:35 +0000</pubDate>
		<dc:creator>CharlyBr</dc:creator>
				<category><![CDATA[Distro]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[lenny]]></category>
		<category><![CDATA[locales]]></category>
		<category><![CDATA[perl]]></category>

		<guid isPermaLink="false">http://charles.lescampeurs.org/?p=152</guid>
		<description><![CDATA[If like me you just have upgraded your Debian system to Lenny, you probably encounter the following warnings while launching perl: perl: warning: Setting locale failed. perl: warning: Please check that your locale settings:         LANGUAGE = (unset),         LC_ALL = (unset),         LANG = "fr_FR.UTF-8"     are supported and installed on your system. perl: [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fcharles.lescampeurs.org%2F2009%2F02%2F24%2Fdebian-lenny-and-perl-locales-warning-messages"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fcharles.lescampeurs.org%2F2009%2F02%2F24%2Fdebian-lenny-and-perl-locales-warning-messages&amp;style=normal" height="61" width="50" /><br />
			</a>
		</div>
<p>If like me you just have upgraded your Debian system to Lenny, you probably encounter the following warnings while launching perl:</p>
<pre>perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
        LANGUAGE = (unset),
        LC_ALL = (unset),
        LANG = "fr_FR.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").</pre>
<p>To get rid of these annoying messages, I&#8217;ve just reconfigured locales with the command:</p>
<pre># dpkg-reconfigure locales</pre>
<p>Choose your locale when you&#8217;re asked for your <em>&#8220;Default locale for the system environment&#8221;.</em></p>
<p>You should have a message like:</p>
<pre>Generating locales (this might take a while)...
  en_US.UTF-8... done
Generation complete.</pre>
<p>Then, logout, login and your perl installation works fine!</p>
]]></content:encoded>
			<wfw:commentRss>http://charles.lescampeurs.org/2009/02/24/debian-lenny-and-perl-locales-warning-messages/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Use multiple memcached daemons on FreeBSD</title>
		<link>http://charles.lescampeurs.org/2008/10/02/use-multiple-memcached-daemons-on-freebsd</link>
		<comments>http://charles.lescampeurs.org/2008/10/02/use-multiple-memcached-daemons-on-freebsd#comments</comments>
		<pubDate>Thu, 02 Oct 2008 10:23:59 +0000</pubDate>
		<dc:creator>CharlyBr</dc:creator>
				<category><![CDATA[Distro]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[FreeBSD]]></category>
		<category><![CDATA[memcached]]></category>

		<guid isPermaLink="false">http://charles.lescampeurs.org/?p=85</guid>
		<description><![CDATA[As you may know, when using memcached on 32-bit servers, processes can only address 4GB of virtual memory making the memcached daemon handle only 2 or 3 Gb of memory. If you want to address more memory, you need to launch multiple memcached daemons. I wrote an rc script , mmemcached, for FreeBSD to manage [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fcharles.lescampeurs.org%2F2008%2F10%2F02%2Fuse-multiple-memcached-daemons-on-freebsd"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fcharles.lescampeurs.org%2F2008%2F10%2F02%2Fuse-multiple-memcached-daemons-on-freebsd&amp;style=normal" height="61" width="50" /><br />
			</a>
		</div>
<p><a href="http://charles.lescampeurs.org/wp-content/uploads/2008/10/picture-7.png"><img class="alignleft size-full wp-image-86" title="memcached" src="http://charles.lescampeurs.org/wp-content/uploads/2008/10/picture-7.png" alt="" width="160" height="160" /></a>As you may know, when using <a title="memcached homepage" href="http://www.danga.com/memcached/" target="_blank">memcached</a> on 32-bit servers, processes can only address 4GB of virtual memory making the memcached daemon handle only 2 or 3 Gb of memory.</p>
<p>If you want to address more memory, you need to launch multiple memcached daemons.</p>
<p>I wrote an rc script , <a title="mmemcached FreeBSD rc script" href="http://github.com/CharlyBr/freebsd-snippets/tree/master/mmemcached" target="_blank">mmemcached</a>, for FreeBSD to manage this.</p>
<p>To use it, you need to add this in /etc/rc.conf:</p>
<pre>mmemcached_enable="YES"
mmemcached_servers="1 2"
mmemcached_user="nobody"
mmemcached_args="-c 8192 -t 2 -m 2048 -d"</pre>
<p>Copy the mmemcached script in /usr/local/etc/rc.d for example and launch it with the start argument. With the above configuration it will launch two memcached daemons listening on ports 11211 and 11212 (mmemcached_servers parameter) with 2Gb of memory.</p>
<h2>Configuration</h2>
<p>Details of the rc.conf configuration:</p>
<ul>
<li>mmemcached_enabled: let this script &#8220;startable&#8221;,</li>
<li>mmemcached_servers: List of the daemons you want to start. Each number is used to generate the port number of the daemon. For example, 2 will launch a daemon listening on port 11212,</li>
<li>mmemcached_user: user that will start the daemon,</li>
<li>mmemcached_args: flags to pass to the daemon.</li>
</ul>
<h2>Download</h2>
<p><a title="mmemcached FreeBSD" href="http://github.com/CharlyBr/freebsd-snippets/tarball/master" target="_blank">Download the script</a> on <a title="FreeBSD snippets" href="http://github.com/CharlyBr/freebsd-snippets/tree/master" target="_blank">github</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://charles.lescampeurs.org/2008/10/02/use-multiple-memcached-daemons-on-freebsd/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Follow your debian server updates by email with apticron</title>
		<link>http://charles.lescampeurs.org/2008/07/30/follow-your-debian-server-updates-by-email-with-apticron</link>
		<comments>http://charles.lescampeurs.org/2008/07/30/follow-your-debian-server-updates-by-email-with-apticron#comments</comments>
		<pubDate>Wed, 30 Jul 2008 05:34:17 +0000</pubDate>
		<dc:creator>CharlyBr</dc:creator>
				<category><![CDATA[Distro]]></category>
		<category><![CDATA[apticron]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://charles.lescampeurs.org/?p=33</guid>
		<description><![CDATA[apticron is a shell script that send you an email report when new packages are available on your debian server. Install apticron As root, do: apt-get install apticron apticron configuration via /etc/apticron/apticron.conf To receive reports on your email change the EMAIL variable in the configuration file. By default, reports are sent to the root user. [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fcharles.lescampeurs.org%2F2008%2F07%2F30%2Ffollow-your-debian-server-updates-by-email-with-apticron"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fcharles.lescampeurs.org%2F2008%2F07%2F30%2Ffollow-your-debian-server-updates-by-email-with-apticron&amp;style=normal" height="61" width="50" /><br />
			</a>
		</div>
<p>apticron is a shell script that send you an email report when new packages are available on your debian server.</p>
<h2>Install apticron</h2>
<p>As root, do:</p>
<pre>apt-get install apticron</pre>
<h2>apticron configuration via /etc/apticron/apticron.conf</h2>
<p>To receive reports on your email change the EMAIL variable in the configuration file. By default, reports are sent to the <em>root</em> user.</p>
<pre>EMAIL="root" -&gt; EMAIL="you@domain.com"</pre>
<h2>Reports received</h2>
<p>Now apticron will send you reports like this:</p>
<pre>apticron report [Sat, 26 Jul 2008 06:45:47 +0200]
==============================================
apticron has detected that some packages need upgrading on:

        localhost.localdomain

        [ <a href="http://127.0.0.1/" target="_blank">127.0.0.1</a> XXX.XXX.XXX.XXX ]

The following packages are currently pending an upgrade:

        lighttpd 1.4.13-4etch10

========================================================================

Package Details:

Reading changelogs...

--- Changes for lighttpd ---

lighttpd (1.4.13-4etch10) stable-security; urgency=low

  [ Pierre Habouzit ]

  * Non-maintainer upload.

  * Fix [CVE-2008-1531] patches mess, and add a missing hunk of the patch.

 -- Thijs Kinkhorst thijs debian org  Tue, 22 Jul 2008 12:19:10 +0200

========================================================================

You can perform the upgrade by issuing the command:

        aptitude dist-upgrade

as root on localhost.localdomain

It is recommended that you simulate the upgrade first to confirm that the actions that
would be taken are reasonable. The upgrade may be simulated by issuing the command:

        aptitude -s -y dist-upgrade

--
apticron</pre>
<h2>Apticron files</h2>
<p>For more informations, you can have a look to those files:</p>
<pre>/etc/cron.daily/apticron
/usr/sbin/apticron</pre>
]]></content:encoded>
			<wfw:commentRss>http://charles.lescampeurs.org/2008/07/30/follow-your-debian-server-updates-by-email-with-apticron/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
