slurmctld - The central management daemon of Slurm.
is the central management daemon of Slurm. It monitors all
other Slurm daemons and resources, accepts work (jobs), and allocates
resources to those jobs. Given the critical functionality of slurmctld
there may be a backup server to assume these functions in the event that the
primary server fails.
- Do not recover state of BlueGene blocks when running on a
- Clear all previous slurmctld state from its last
checkpoint. With this option, all jobs, including both running and queued,
and all node states, will be deleted. Without this option, previously
running jobs will be preserved along with node State of DOWN,
DRAINED and DRAINING nodes and the associated Reason field for
those nodes. NOTE: It is rare you would ever want to use this in
production as all jobs will be killed.
- Run slurmctld in the foreground with logging copied
- -f <file>
- Read configuration from the specified file. See
- Help; print a brief summary of command options.
- -L <file>
- Write log messages to the specified file.
- -n <value>
- Set the daemon's nice value to the specified value,
typically a negative number.
- Recover partial state from last checkpoint: jobs and node
DOWN/DRAIN state and reason information state. No partition state is
recovered. This is the default action.
- Recover full state from last checkpoint: jobs, node, and
partition state. Without this option, previously running jobs will be
preserved along with node State of DOWN, DRAINED and DRAINING nodes
and the associated Reason field for those nodes. No other node or
partition state will be preserved.
- Verbose operation. Multiple -v's increase
- Print version information and exit.
The following environment variables can be used to override settings compiled
- The location of the Slurm configuration file. This is
overridden by explicitly naming a configuration file on the command line.
If slurmctld is started with the -D
option then the core file will be
written to the current working directory. Otherwise if SlurmctldLogFile
is a fully qualified path name (starting with a slash), the core file will be
written to the same directory as the log file, provided SlurmUser has write
permission on the directory. Otherwise the core file will be written to the
, or "/var/tmp/" as a last resort. If none
of the above directories have write permission for SlurmUser, no core file
will be produced. The command "scontrol abort" can be used to abort
the slurmctld daemon and generate a core file.
It may be useful to experiment with different slurmctld
configuration parameters using a distinct configuration file (e.g. timeouts).
However, this special configuration file will not be used by the slurmd
daemon or the Slurm programs, unless you specifically tell each of them to use
it. If you desire changing communication ports, the location of the temporary
file system, or other parameters used by other Slurm components, change the
common configuration file, slurm.conf
Copyright (C) 2002-2007 The Regents of the University of California. Copyright
(C) 2008-2010 Lawrence Livermore National Security. Produced at Lawrence
Livermore National Laboratory (cf, DISCLAIMER). CODE-OCEC-09-009. All rights
This file is part of Slurm, a resource management program. For details, see
Slurm is free software; you can redistribute it and/or modify it under the terms
of the GNU General Public License as published by the Free Software
Foundation; either version 2 of the License, or (at your option) any later
Slurm is distributed in the hope that it will be useful, but WITHOUT ANY
WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR
A PARTICULAR PURPOSE. See the GNU General Public License for more details.