<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE rss [<!ENTITY % HTMLlat1 PUBLIC "-//W3C//ENTITIES Latin 1 for XHTML//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent">]>
<rss version="2.0" xml:base="http://lopsa.org">
<channel>
 <title>League of Professional System Administrators - Unix</title>
 <link>http://lopsa.org/taxonomy/term/25/0</link>
 <description></description>
 <language>en</language>
<item>
 <title>Notes on accessing SVN over SSH</title>
 <link>http://lopsa.org/node/1671</link>
 <description>&lt;/p&gt;
&lt;pre &gt;

Here are my notes how I set up SVN over SSH to an SVN server that had been set up to run SVN as a single user, &quot;svn&quot;.

So, we have multiple users on the remote side, all logging in as &quot;svn&quot; on the SVN server side.
Authentication is done via a dedicated key-pair, with special options to make SVN+SSH work.

See &lt;a href=&quot;http://svn.collab.net/repos/svn/trunk/notes/ssh-tricks&quot;&gt;http://svn.collab.net/repos/svn/trunk/notes/ssh-tricks&lt;/a&gt; for more details.

These are just my notes, the above link is authoritative.


Procedure:

1. Generate a dedicated key pair

	[SVN Client]$ ssh-keygen -f ~/.ssh/svnssh
	Generating public/private rsa key pair.
	Created directory &#039;/home/tsalolia/.ssh&#039;.
&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/1671&quot; dc:identifier=&quot;http://lopsa.org/node/1671&quot; dc:title=&quot;Notes on accessing SVN over SSH&quot; trackback:ping=&quot;http://lopsa.org/trackback/1671&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <category domain="http://lopsa.org/taxonomy/term/25">Unix</category>
 <pubDate>Fri, 26 Sep 2008 12:32:00 -0700</pubDate>
 <author>Aleksey Tsalolikhin</author>
</item>
<item>
 <title>Grub-booting memtest86 on x86 hardware</title>
 <link>http://lopsa.org/node/1644</link>
 <description>&lt;p&gt;It is trivial to set things up so you are able to select memtest86 as a boot option in GRUB:&lt;/p&gt;
&lt;p&gt;Download the latest memtest source from &lt;a href=&quot;http://www.memtest86.com&quot;&gt;http://www.memtest86.com&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Extract and follow the instructions in the README that comes with it to compile.  Copy the resulting memtest.bin to /boot and edit /etc/grub.conf to have the following 3 lines:&lt;/p&gt;
&lt;pre &gt;
title Memtest86
        root (hd0,0)
        kernel /boot/memtest.bin
&lt;/pre&gt;&lt;p&gt;
Make sure you reboot to test.&lt;/p&gt;
&lt;p&gt;In theory this should work with any x86 OS + bootloader. I am doing this with RHEL 4 + GRUB.&lt;/p&gt;

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/1644&quot; dc:identifier=&quot;http://lopsa.org/node/1644&quot; dc:title=&quot;Grub-booting memtest86 on x86 hardware&quot; trackback:ping=&quot;http://lopsa.org/trackback/1644&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <category domain="http://lopsa.org/taxonomy/term/26">Linux</category>
 <category domain="http://lopsa.org/taxonomy/term/25">Unix</category>
 <pubDate>Tue, 08 Jul 2008 09:28:24 -0700</pubDate>
 <author>nomad</author>
</item>
<item>
 <title>Mixing Multiple Volume Managers (especially ZFS and VxVM)</title>
 <link>http://lopsa.org/node/1641</link>
 <description>&lt;p&gt;I&#039;ve recently had a number of projects at work that want to mix multiple volume managers on a single server, specifically &lt;span class=&quot;caps&quot;&gt;ZFS &lt;/span&gt;and VxVM for &lt;span class=&quot;caps&quot;&gt;SAN &lt;/span&gt;volumes (actually, three including &lt;span class=&quot;caps&quot;&gt;SVM &lt;/span&gt;for internal boot disk mirroring).  The projects generally are for database servers, and want to use VxVM for database volumes because &lt;span class=&quot;caps&quot;&gt;ZFS &lt;/span&gt;currently has some serious limitation on database size (limited number of devices recommended in a single zpool) and performance (single threaded checksumming, for one).  However, at the same time, they want to have access to some of &lt;span class=&quot;caps&quot;&gt;ZFS&#039;&lt;/span&gt;s features (in particular, the ability to oversubscribe filesystems, dynamic resize, snapshots and rollback) for some of the other filesystems.&lt;/p&gt;
&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/1641&quot; dc:identifier=&quot;http://lopsa.org/node/1641&quot; dc:title=&quot;Mixing Multiple Volume Managers (especially ZFS and VxVM)&quot; trackback:ping=&quot;http://lopsa.org/trackback/1641&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <category domain="http://lopsa.org/taxonomy/term/34">Process</category>
 <category domain="http://lopsa.org/taxonomy/term/156">Storage</category>
 <category domain="http://lopsa.org/taxonomy/term/25">Unix</category>
 <pubDate>Mon, 07 Jul 2008 13:15:13 -0700</pubDate>
 <author>spp</author>
</item>
<item>
 <title>Heartbeat / Linux-HA</title>
 <link>http://lopsa.org/node/1526</link>
 <description>&lt;div class=&quot;flexinode-body flexinode-4&quot;&gt;&lt;div class=&quot;flexinode-textfield-13&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Short Description:&lt;/label&gt;&lt;br /&gt;
 Failover and availability clustering for *nix systems
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Home Page:&lt;/label&gt;&lt;br /&gt;
 &lt;a href=&quot;http://linux-ha.org&quot;&gt;linux-ha.org&lt;/a&gt;
&lt;/div&gt;
&lt;div class=&quot;flexinode-timestamp-15&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Release Date:&lt;/label&gt;&lt;br /&gt;
 Wed, 1998-03-18 10:58
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-select-18&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Status:&lt;/label&gt;&lt;br /&gt;
 Mature
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-textarea-17&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Long Description:&lt;/label&gt;&lt;br /&gt;
 &lt;p&gt;Linux-HA aka Heartbeat is a modular package to control high-availability clustering. In spite of it&#039;s name it is not limited to Linux (although that is the primary platform), It has an automake based compile and has been used on *BSD, Solaris, and to some extent on AIX as well.&lt;/p&gt;
&lt;p&gt;It can hearbeat in multiple ways (UDP broadcast, multicast, and unicast as well as over serial ports, although the serial port heartbeat has been accidently broken in some versions), and over multiple channels (up to 32 as of the time of writing)&lt;/p&gt;
&lt;p&gt;It can support sub-second failover&lt;/p&gt;
&lt;p&gt;It delays heartbeat checking on initial boot to allow switches time to get through their spanning tree detection timeouts.&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/1526&quot; dc:identifier=&quot;http://lopsa.org/node/1526&quot; dc:title=&quot;Heartbeat / Linux-HA&quot; trackback:ping=&quot;http://lopsa.org/trackback/1526&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <category domain="http://lopsa.org/taxonomy/term/169">Availability</category>
 <category domain="http://lopsa.org/taxonomy/term/25">Unix</category>
 <pubDate>Tue, 16 Oct 2007 22:51:19 -0700</pubDate>
 <author>dlang</author>
</item>
<item>
 <title>Notes on *nix atime</title>
 <link>http://lopsa.org/node/1502</link>
 <description>&lt;p&gt;Read an interesting discussion on the lkml list where Linus and friends talked about atime&#039;s performance impacts (&lt;a href=&quot;http://kerneltrap.org/node/14148&quot;&gt;http://kerneltrap.org/node/14148&lt;/a&gt;).  Ingo phrased the problem best with:&lt;/p&gt;
&lt;p&gt;     &#039; For every file that is read from the disk, lets do a ... write to&lt;br /&gt;
     the disk! And, for every file that is already cached and which we&lt;br /&gt;
     read from the cache ... do a write to the disk! &#039;&lt;/p&gt;
&lt;p&gt;Solutions are to mount your file systems with the noatime, nodiratime options.  The only time this may cause a problem is if you have a local mail spool (the mailer will not know that new email arrived) or possibly with some backup software.&lt;/p&gt;

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/1502&quot; dc:identifier=&quot;http://lopsa.org/node/1502&quot; dc:title=&quot;Notes on *nix atime&quot; trackback:ping=&quot;http://lopsa.org/trackback/1502&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <category domain="http://lopsa.org/taxonomy/term/26">Linux</category>
 <category domain="http://lopsa.org/taxonomy/term/155">Performance Tuning</category>
 <category domain="http://lopsa.org/taxonomy/term/25">Unix</category>
 <pubDate>Thu, 09 Aug 2007 12:53:38 -0700</pubDate>
 <author>ski</author>
</item>
<item>
 <title>ifinput </title>
 <link>http://lopsa.org/node/1477</link>
 <description>&lt;div class=&quot;flexinode-body flexinode-4&quot;&gt;&lt;div class=&quot;flexinode-textfield-13&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Short Description:&lt;/label&gt;&lt;br /&gt;
 A wrapper command to run another command if there is any output on stdout
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Home Page:&lt;/label&gt;&lt;br /&gt;
 &lt;a href=&quot;http://www.generalconcepts.com/resources/software/&quot;&gt;www.generalconcepts.com/resources/software/&lt;/a&gt;
&lt;/div&gt;
&lt;div class=&quot;flexinode-timestamp-15&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Release Date:&lt;/label&gt;&lt;br /&gt;
 Wed, 2001-02-14 15:00
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-select-18&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Status:&lt;/label&gt;&lt;br /&gt;
 Stable
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-textarea-17&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Long Description:&lt;/label&gt;&lt;br /&gt;
 &lt;p&gt;Often Unix system administrators need an easy way to redirect any stderr output generated from crontab entries to a specific email address.  With the ifinput binary, it&#039;s simple.  For example:&lt;/p&gt;
&lt;p&gt;20 8 * * * /usr/local/sbin/daily_stuff.sh 2&gt;&amp;amp;1 | /usr/local/bin/ifinput mailx -s &quot;Error: daily_stuff.sh&quot; &lt;a href=&quot;mailto:system-errors@foo.org&quot;&gt;system-errors@foo.org&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Just arrange the crontab entries so that the periodic jobs don&#039;t generate stdout unless there&#039;s something interesting there.  Then redirect stderr to stdout and pipe both to ifinput.&lt;/p&gt;
&lt;p&gt;ifinput can be used in a variety of different scenarios, not just cron jobs.&lt;br /&gt;
The source code is available here:  &lt;a href=&quot;http://www.generalconcepts.com/resources/software/gctools-1.0.tar.gz&quot;&gt;http://www.generalconcepts.com/resources/software/gctools-1.0.tar.gz&lt;/a&gt;&lt;br /&gt;
It has a very small footprint and will compile without issue on most unix systems.&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/1477&quot; dc:identifier=&quot;http://lopsa.org/node/1477&quot; dc:title=&quot;ifinput &quot; trackback:ping=&quot;http://lopsa.org/trackback/1477&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <category domain="http://lopsa.org/taxonomy/term/167">System management</category>
 <category domain="http://lopsa.org/taxonomy/term/25">Unix</category>
 <pubDate>Fri, 06 Jul 2007 16:12:20 -0700</pubDate>
 <author>jm</author>
</item>
<item>
 <title>Bcfg2</title>
 <link>http://lopsa.org/node/1156</link>
 <description>&lt;div class=&quot;flexinode-body flexinode-4&quot;&gt;&lt;div class=&quot;flexinode-textfield-13&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Short Description:&lt;/label&gt;&lt;br /&gt;
 Bcfg2 is a centralized configuration tool that provides reconciliation of the current actual configuration with a specification.
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Home Page:&lt;/label&gt;&lt;br /&gt;
 &lt;a href=&quot;http://trac.mcs.anl.gov/projects/bcfg2&quot;&gt;trac.mcs.anl.gov/projects/bcfg2&lt;/a&gt;
&lt;/div&gt;
&lt;div class=&quot;flexinode-timestamp-15&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Release Date:&lt;/label&gt;&lt;br /&gt;
 Wed, 2004-10-06 15:48
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-select-18&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Status:&lt;/label&gt;&lt;br /&gt;
 Stable
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-textarea-17&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Long Description:&lt;/label&gt;&lt;br /&gt;
 &lt;p&gt;Bcfg2 is a generative configuration management system that can be used for management of aspects of client systems, complete control of client systems, and the range in between. Bcfg2 is designed to work well in pre-existing environments, and in the presence of manual administration.&lt;br /&gt;
Bcfg2&#039;s most interesting feature is a web frontend that presents client configuration conformance information to administrators. This provides administrators with a direct way to observe how good of a job they are doing describing how their network should look. To our knowledge, this approach is unique to bcfg2, both as a goal and as a supported operation.&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/1156&quot; dc:identifier=&quot;http://lopsa.org/node/1156&quot; dc:title=&quot;Bcfg2&quot; trackback:ping=&quot;http://lopsa.org/trackback/1156&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <category domain="http://lopsa.org/taxonomy/term/163">Configuration Mgmt</category>
 <category domain="http://lopsa.org/taxonomy/term/25">Unix</category>
 <pubDate>Sat, 10 Feb 2007 12:02:18 -0800</pubDate>
 <author>nld</author>
</item>
<item>
 <title>Django</title>
 <link>http://lopsa.org/node/996</link>
 <description>&lt;div class=&quot;flexinode-body flexinode-4&quot;&gt;&lt;div class=&quot;flexinode-textfield-13&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Short Description:&lt;/label&gt;&lt;br /&gt;
 Excellent Python web development framework
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Home Page:&lt;/label&gt;&lt;br /&gt;
 &lt;a href=&quot;http://www.djangoproject.com&quot;&gt;www.djangoproject.com&lt;/a&gt;
&lt;/div&gt;
&lt;div class=&quot;flexinode-timestamp-15&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Release Date:&lt;/label&gt;&lt;br /&gt;
 Fri, 2005-07-15 14:00
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-select-18&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Status:&lt;/label&gt;&lt;br /&gt;
 Stable
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-textarea-17&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Long Description:&lt;/label&gt;&lt;br /&gt;
 &lt;p&gt;I like to use this to throw together nice web frontends for the PHBs to look at stats &amp;amp; stuff.  It&#039;s pretty simple to use, interfaces easily to a database--very useful for the sorts of sysadmin-plus stuff I tend to do.&lt;/p&gt;

&lt;/div&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/996&quot; dc:identifier=&quot;http://lopsa.org/node/996&quot; dc:title=&quot;Django&quot; trackback:ping=&quot;http://lopsa.org/trackback/996&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <category domain="http://lopsa.org/taxonomy/term/28">Applications</category>
 <category domain="http://lopsa.org/taxonomy/term/29">Database</category>
 <category domain="http://lopsa.org/taxonomy/term/26">Linux</category>
 <category domain="http://lopsa.org/taxonomy/term/145">Software Development</category>
 <category domain="http://lopsa.org/taxonomy/term/25">Unix</category>
 <category domain="http://lopsa.org/taxonomy/term/27">Windows</category>
 <category domain="http://lopsa.org/taxonomy/term/33">WWW</category>
 <pubDate>Mon, 22 Jan 2007 13:08:07 -0800</pubDate>
 <author>eadmund</author>
</item>
<item>
 <title>NMAP</title>
 <link>http://lopsa.org/node/980</link>
 <description>&lt;div class=&quot;flexinode-body flexinode-4&quot;&gt;&lt;div class=&quot;flexinode-textfield-13&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Short Description:&lt;/label&gt;&lt;br /&gt;
 Fast enumeration of network services
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Home Page:&lt;/label&gt;&lt;br /&gt;
 &lt;a href=&quot;http://insecure.org/nmap&quot;&gt;insecure.org/nmap&lt;/a&gt;
&lt;/div&gt;
&lt;div class=&quot;flexinode-timestamp-15&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Release Date:&lt;/label&gt;&lt;br /&gt;
 Sun, 2007-01-14 10:00
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-select-18&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Status:&lt;/label&gt;&lt;br /&gt;
 Active
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-textarea-17&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Long Description:&lt;/label&gt;&lt;br /&gt;
 &lt;p&gt;Nmap is a powerful tool for discovering hosts on a network and enumerating what service they are offering. This can be used to find vulnerable systems, to locate rogue services on your network or simply for a first step in troubleshooting.&lt;/p&gt;

&lt;/div&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/980&quot; dc:identifier=&quot;http://lopsa.org/node/980&quot; dc:title=&quot;NMAP&quot; trackback:ping=&quot;http://lopsa.org/trackback/980&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <category domain="http://lopsa.org/taxonomy/term/140">Communications</category>
 <category domain="http://lopsa.org/taxonomy/term/26">Linux</category>
 <category domain="http://lopsa.org/taxonomy/term/46">Network</category>
 <category domain="http://lopsa.org/taxonomy/term/21">Networking</category>
 <category domain="http://lopsa.org/taxonomy/term/24">Operating System</category>
 <category domain="http://lopsa.org/taxonomy/term/47">Operating System</category>
 <category domain="http://lopsa.org/taxonomy/term/119">Protocols</category>
 <category domain="http://lopsa.org/taxonomy/term/44">Security</category>
 <category domain="http://lopsa.org/taxonomy/term/114">TCP</category>
 <category domain="http://lopsa.org/taxonomy/term/23">UDP</category>
 <category domain="http://lopsa.org/taxonomy/term/25">Unix</category>
 <category domain="http://lopsa.org/taxonomy/term/137">User Security</category>
 <category domain="http://lopsa.org/taxonomy/term/134">Visualization</category>
 <category domain="http://lopsa.org/taxonomy/term/27">Windows</category>
 <pubDate>Sun, 14 Jan 2007 09:50:04 -0800</pubDate>
 <author>dklein</author>
</item>
<item>
 <title>The latest admin trick I learned...</title>
 <link>http://lopsa.org/node/931</link>
 <description>&lt;p&gt;Although LOPSA is platform-agnostic, my current job has me solidly as a Solaris and EMC storage admin.  I have experience on just about every other platform of at least a limited extent (DEC UNIX, SCO, HPUX, Windows 4.0, 2000, 2003, Linux mainly RedHat, FreeBSD, OSX, etc...).  However all the new tricks I learn, most are going to be on the Solaris platform.&lt;/p&gt;
&lt;p&gt;The latest two things I had to learn are how to handle shared memory allocations under Solaris 10, and the &#039;supported&#039; way to make Veritas filesystems mounted in a zone.&lt;/p&gt;
&lt;p&gt;Shared memory was interesting, I mainly googled and asked around until I got a couple of command lines.  Then when that didn&#039;t work quite as expected in a zone, I borrowed a copy of the new Solaris Internals books to see if I was doing something wrong.  Turns out I wasn&#039;t really, I just seemed to be running the box out of memory completely.&lt;/p&gt;

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/931&quot; dc:identifier=&quot;http://lopsa.org/node/931&quot; dc:title=&quot;The latest admin trick I learned...&quot; trackback:ping=&quot;http://lopsa.org/trackback/931&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <category domain="http://lopsa.org/taxonomy/term/25">Unix</category>
 <pubDate>Wed, 20 Dec 2006 08:02:49 -0800</pubDate>
 <author>bwilson</author>
</item>
<item>
 <title>daemontools</title>
 <link>http://lopsa.org/node/846</link>
 <description>&lt;div class=&quot;flexinode-body flexinode-4&quot;&gt;&lt;div class=&quot;flexinode-textfield-13&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Short Description:&lt;/label&gt;&lt;br /&gt;
 daemontools is a collection of tools for managing UNIX services
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Home Page:&lt;/label&gt;&lt;br /&gt;
 &lt;a href=&quot;http://cr.yp.to/daemontools.html&quot;&gt;cr.yp.to/daemontools.html&lt;/a&gt;
&lt;/div&gt;
&lt;div class=&quot;flexinode-timestamp-15&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Release Date:&lt;/label&gt;&lt;br /&gt;
 Tue, 2000-11-07 21:00
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-select-18&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Status:&lt;/label&gt;&lt;br /&gt;
 Mature
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-textarea-17&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Long Description:&lt;/label&gt;&lt;br /&gt;
 &lt;p&gt;daemontools is a collection of tools for managing UNIX services.&lt;/p&gt;
&lt;p&gt;supervise monitors a service. It starts the service and restarts the service if it dies. Setting up a new service is easy: all supervise needs is a directory with a run script that runs the service.&lt;/p&gt;
&lt;p&gt;multilog saves error messages to one or more logs. It optionally timestamps each line and, for each log, includes or excludes lines matching specified patterns. It automatically rotates logs to limit the amount of disk space used. If the disk fills up, it pauses and tries again, without losing any data. &lt;/p&gt;
&lt;p&gt;A less encumbered version is available at &lt;a href=&quot;http://smarden.org/runit/&quot;&gt;http://smarden.org/runit/&lt;/a&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/846&quot; dc:identifier=&quot;http://lopsa.org/node/846&quot; dc:title=&quot;daemontools&quot; trackback:ping=&quot;http://lopsa.org/trackback/846&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <category domain="http://lopsa.org/taxonomy/term/151">Log Data</category>
 <category domain="http://lopsa.org/taxonomy/term/150">Operating System</category>
 <category domain="http://lopsa.org/taxonomy/term/25">Unix</category>
 <pubDate>Sat, 21 Oct 2006 21:04:48 -0700</pubDate>
 <author>doug</author>
</item>
<item>
 <title>Dtrace quick reference</title>
 <link>http://lopsa.org/DtraceQuickref</link>
 <description>&lt;div class=&quot;flexinode-body flexinode-4&quot;&gt;&lt;div class=&quot;flexinode-textfield-13&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Short Description:&lt;/label&gt;&lt;br /&gt;
 DTrace Quick Reference Guide
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Home Page:&lt;/label&gt;&lt;br /&gt;
 &lt;a href=&quot;http://developers.sun.com/solaris/articles/dtrace_quickref/dtrace_quickref.html&quot;&gt;developers.sun.com/solaris/articles/dtrace_quickref/dtrace_quickref.html&lt;/a&gt;
&lt;/div&gt;
&lt;div class=&quot;flexinode-timestamp-15&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Release Date:&lt;/label&gt;&lt;br /&gt;
 Thu, 2006-09-21 12:00
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-select-18&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Status:&lt;/label&gt;&lt;br /&gt;
 New
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-textarea-17&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Long Description:&lt;/label&gt;&lt;br /&gt;
 &lt;blockquote &gt;&lt;p&gt;DTrace is a comprehensive dynamic tracing facility that is built into the Solaris OS. DTrace can be used by administrators and developers, and can safely be used on live production systems. DTrace enables you to examine the behavior of user programs as well as the behavior of the operating system. Users of DTrace can create custom programs with the D scripting language. Custom programs provide the ability to dynamically instrument the system. Custom programs provide immediate, concise answers to specific questions about the behavior of particular applications.&lt;/p&gt;&lt;/blockquote&gt;

&lt;/div&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/DtraceQuickref&quot; dc:identifier=&quot;http://lopsa.org/DtraceQuickref&quot; dc:title=&quot;Dtrace quick reference&quot; trackback:ping=&quot;http://lopsa.org/trackback/787&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <category domain="http://lopsa.org/taxonomy/term/28">Applications</category>
 <category domain="http://lopsa.org/taxonomy/term/24">Operating System</category>
 <category domain="http://lopsa.org/taxonomy/term/150">Operating System</category>
 <category domain="http://lopsa.org/taxonomy/term/25">Unix</category>
 <pubDate>Thu, 21 Sep 2006 12:59:34 -0700</pubDate>
 <author>doug</author>
</item>
<item>
 <title>rsyslog</title>
 <link>http://lopsa.org/tool_rsyslog</link>
 <description>&lt;div class=&quot;flexinode-body flexinode-4&quot;&gt;&lt;div class=&quot;flexinode-textfield-13&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Short Description:&lt;/label&gt;&lt;br /&gt;
 Rsyslog is an enhanced multi-threaded syslogd supporting, among others, MySQL, syslog/tcp, RFC 3195, permitted sender lists, fil
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Home Page:&lt;/label&gt;&lt;br /&gt;
 &lt;a href=&quot;http://www.rsyslog.com&quot;&gt;www.rsyslog.com&lt;/a&gt;
&lt;/div&gt;
&lt;div class=&quot;flexinode-timestamp-15&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Release Date:&lt;/label&gt;&lt;br /&gt;
 Fri, 2005-09-23 20:00
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-select-18&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Status:&lt;/label&gt;&lt;br /&gt;
 Active
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-textarea-17&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Long Description:&lt;/label&gt;&lt;br /&gt;
 &lt;p&gt;Rsyslog is an enhanced multi-threaded syslogd supporting, among others, MySQL, syslog/tcp, RFC 3195, permitted sender lists, filtering on any message part, and fine grain output format control. It is quite compatible to stock sysklogd and can be used as a drop-in replacement. Its advanced features make it suitable for enterprise-class, encryption protected syslog relay chains while at the same time being very easy to setup for the novice user. An optional web interface - &lt;a href=&quot;http://www.phplogcon.com/&quot;&gt;phpLogCon&lt;/a&gt; - can be used to visualize all data online.&lt;/p&gt;

&lt;/div&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/tool_rsyslog&quot; dc:identifier=&quot;http://lopsa.org/tool_rsyslog&quot; dc:title=&quot;rsyslog&quot; trackback:ping=&quot;http://lopsa.org/trackback/754&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <category domain="http://lopsa.org/taxonomy/term/28">Applications</category>
 <category domain="http://lopsa.org/taxonomy/term/140">Communications</category>
 <category domain="http://lopsa.org/taxonomy/term/46">Network</category>
 <category domain="http://lopsa.org/taxonomy/term/24">Operating System</category>
 <category domain="http://lopsa.org/taxonomy/term/47">Operating System</category>
 <category domain="http://lopsa.org/taxonomy/term/150">Operating System</category>
 <category domain="http://lopsa.org/taxonomy/term/44">Security</category>
 <category domain="http://lopsa.org/taxonomy/term/143">Security</category>
 <category domain="http://lopsa.org/taxonomy/term/25">Unix</category>
 <pubDate>Sun, 27 Aug 2006 20:47:42 -0700</pubDate>
 <author>doug</author>
</item>
</channel>
</rss>
