<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://docs-archive.hpc.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>hpc documentation - abstract:caviness:runjobs</title>
        <description></description>
        <link>https://docs-archive.hpc.udel.edu/</link>
        <lastBuildDate>Wed, 15 Apr 2026 08:02:51 +0000</lastBuildDate>
        <generator>FeedCreator 1.8</generator>
        <image>
            <url>https://docs-archive.hpc.udel.edu/_media/wiki/dokuwiki.svg</url>
            <title>hpc documentation</title>
            <link>https://docs-archive.hpc.udel.edu/</link>
        </image>
        <item>
            <title>job_status</title>
            <link>https://docs-archive.hpc.udel.edu/abstract/caviness/runjobs/job_status</link>
            <description>&lt;booktoc/&gt;

Managing Jobs on Caviness

Once a user has been able to submit jobs to the cluster -- interactive or batch -- the user will from time to time want to know what those jobs are doing.  Is the job waiting in a queue for resources to become available, or is it executing?  How long has the job been executing? How much CPU time or memory has the job consumed?  Users can query Slurm for job information using the</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Thu, 23 May 2024 16:08:58 +0000</pubDate>
        </item>
        <item>
            <title>queues</title>
            <link>https://docs-archive.hpc.udel.edu/abstract/caviness/runjobs/queues</link>
            <description>The job queues (partitions) on Caviness

The Caviness cluster has several kinds of partition (queue) available in which to run jobs:
KindDescriptionNodesstandardThe default partition if no --partition submission flag is specified; jobs can be preempted (killed)</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Tue, 30 May 2023 17:48:45 +0000</pubDate>
        </item>
        <item>
            <title>runjobs</title>
            <link>https://docs-archive.hpc.udel.edu/abstract/caviness/runjobs/runjobs</link>
            <description>Running applications on Caviness

Introduction

The Slurm workload manager (job scheduling system) is used to manage and control the resources available to computational tasks.  The job scheduler considers each job&#039;s resource requests (memory, disk space, processor cores) and executes it as those resources become available.  As a cluster workload manager, Slurm has three key functions: (1) It allocates exclusive and/or non-exclusive access to resources (compute nodes) to users for some duration …</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Thu, 05 May 2022 15:17:59 +0000</pubDate>
        </item>
        <item>
            <title>schedule_jobs</title>
            <link>https://docs-archive.hpc.udel.edu/abstract/caviness/runjobs/schedule_jobs</link>
            <description>Scheduling Jobs on Caviness
workgroupinvesting-entity

For example,


[traine@login00 ~]$ workgroup -g it_css
[(it_css:traine)@login00 ~]$


will set the workgroup to it_css for account traine which is reflected in the prompt change [(it_css:traine)@login00 ~]$</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Fri, 30 Jan 2026 01:06:01 +0000</pubDate>
        </item>
        <item>
            <title>sidebar</title>
            <link>https://docs-archive.hpc.udel.edu/abstract/caviness/runjobs/sidebar</link>
            <description>*  Home
	*  Caviness
				*  Request Account
				*  Connecting
				*  Storage
				*  Transfer Files
				*  Application Development
				*  Install Software
				*  Run Jobs
					*  Queues
					*  Schedule Jobs 
					*  Managing Jobs

				*  System Status

	*  DARWIN
	*  Farber (Retired)
	*  Mills (Retired)
	*  Software
	*  Training
	*  Technical</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Thu, 16 Mar 2023 14:55:52 +0000</pubDate>
        </item>
    </channel>
</rss>
