<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="http://beren.engr.udel.edu/lib/exe/css.php?s=feed" type="text/css"?>
<rss version="2.0">
    <channel xmlns:g="http://base.google.com/ns/1.0">
        <title>UDCECC Wiki</title>
        <description></description>
        <link>http://beren.engr.udel.edu/</link>
        <lastBuildDate>Fri, 24 Apr 2026 10:33:05 +0000</lastBuildDate>
        <generator>FeedCreator 1.8</generator>
        <image>
            <url>http://beren.engr.udel.edu/lib/tpl/bootstrap3/images/favicon.ico</url>
            <title>UDCECC Wiki</title>
            <link>http://beren.engr.udel.edu/</link>
        </image>
        <item>
            <title>caviness:login - [Shell customization] </title>
            <link>http://beren.engr.udel.edu/caviness/login?rev=1604934862</link>
            <description>Round-robin DNS load balancing returns multiple IP addresses when the name</description>
            <author>frey@undisclosed.example.com (frey)</author>
        <category>caviness</category>
            <pubDate>Mon, 09 Nov 2020 15:14:22 +0000</pubDate>
        </item>
        <item>
            <title>caviness:slurm-manual:intro - [What are resources?] </title>
            <link>http://beren.engr.udel.edu/caviness/slurm-manual/intro?rev=1566587623</link>
            <description>Getting work done:  what is job scheduling?

The idea of work on a computer system means entering data (input), running programs that make use of the data, and analyzing the data produced (output).  The term programs equates with two entities on Linux systems:</description>
            <author>frey@undisclosed.example.com (frey)</author>
        <category>caviness:slurm-manual</category>
            <pubDate>Fri, 23 Aug 2019 19:13:43 +0000</pubDate>
        </item>
        <item>
            <title>caviness:slurm-manual:start</title>
            <link>http://beren.engr.udel.edu/caviness/slurm-manual/start?rev=1565283176</link>
            <description>Slurm User Manual

Paramount to anyone's successful use of the Caviness cluster is an understanding of job scheduling, specifically how Slurm -- the Simple Linux Utility for Resource Management -- is used on the cluster.  This manual does not attempt to document Slurm in any extensive depth, since that information already exists</description>
            <author>frey@undisclosed.example.com (frey)</author>
        <category>caviness:slurm-manual</category>
            <pubDate>Thu, 08 Aug 2019 16:52:56 +0000</pubDate>
        </item>
        <item>
            <title>caviness:slurm-manual:sidebar</title>
            <link>http://beren.engr.udel.edu/caviness/slurm-manual/sidebar?rev=1565283107</link>
            <description>*  Slurm user manual
		*  Getting work done: what is job scheduling?
		*  Writing job scripts
		*  Submitting job scripts
		*  Checking job progress
		*  Advanced topics
		*  Frequently-asked questions</description>
            <author>frey@undisclosed.example.com (frey)</author>
        <category>caviness:slurm-manual</category>
            <pubDate>Thu, 08 Aug 2019 16:51:47 +0000</pubDate>
        </item>
        <item>
            <title>caviness:resources - [Generation 1] </title>
            <link>http://beren.engr.udel.edu/caviness/resources?rev=1561728906</link>
            <description>Resources

The design of Caviness is similar to previous community clusters.

Compute

Designed as a multi-generational system, over time Caviness will host a variety of nodes, differing not just in memory sizes and presence of coprocessors but also in processor microarchitecture.</description>
            <author>frey@undisclosed.example.com (frey)</author>
        <category>caviness</category>
            <pubDate>Fri, 28 Jun 2019 13:35:06 +0000</pubDate>
        </item>
    </channel>
</rss>
