slurmd - The compute node daemon for Slurm.
is the compute node daemon of Slurm. It monitors all tasks running
on the compute node , accepts work (tasks), launches tasks, and kills running
tasks upon request.
- Report node rebooted when daemon restarted. Used for
- Clear system locks as needed. This may be required if
slurmd terminated abnormally.
- Print actual hardware configuration and exit. The format of
output is the same as used in slurm.conf to describe a node's
configuration plus it's uptime.
- -d <file>
- Specify the fully qualified pathname to the
slurmstepd program to be used for shepherding user job steps. This
can be useful for testing purposes.
- Run slurmd in the foreground. Error and debug messages will
be copied to stderr.
- -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.
- Lock slurmd pages into system memory using mlockall (2) to
disable paging of the slurmd process. This may help in cases where nodes
are marked DOWN during periods of heavy swap activity. If the mlockall (2)
system call is not available, an error will be printed to the log and
slurmd will continue as normal.
- -n <value>
- Set the daemon's nice value to the specified value,
typically a negative number. Also note the PropagatePrioProcess
- -N <hostname>
- Run the daemon with the given hostname. Used to emulate a
larger system with more than one slurmd daemon per node. Requires that
Slurm be built using the --enable-multiple-slurmd configure option.
- Verbose operation. Multiple -v's increase verbosity.
- 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 slurmd is started with the -D
option then the core file will be
written to the current working directory. Otherwise if SlurmdLogFile
a fully qualified path name (starting with a slash), the core file will be
written to the same directory as the log file. Otherwise the core file will be
written to the SlurmSpoolDir
directory, or "/var/tmp/" as a
last resort. If none of the above directories can be written, no core file
will be produced.
It may be useful to experiment with different slurmd
configuration parameters using a distinct configuration file (e.g. timeouts).
However, this special configuration file will not be used by the
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. Copyright (C) 2010-2016
SchedMD LLC. Produced at Lawrence Livermore National Laboratory (cf,
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.