SchedMD - Slurm Support – Full Text Ticket Listing
- Home
- | New
- | Browse
- | Search
- | [?]
- | Reports
- | Help
- | New Account
- | Log In
- | Forgot Password
| Summary: | gres.conf File= option clarification | ||
|---|---|---|---|
| Product: | Slurm | Reporter: | Kilian Cavalotti <kilian> |
| Component: | Documentation | Assignee: | Moe Jette <jette> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | 4 - Minor Issue | ||
| Priority: | --- | CC: | brian, da |
| Version: | 14.11.7 | ||
| Hardware: | Linux | ||
| OS: | Linux | ||
| Site: | Stanford | Alineos Sites: | --- |
| Atos/Eviden Sites: | --- | Confidential Site: | --- |
| Coreweave sites: | --- | Cray Sites: | --- |
| DS9 clusters: | --- | HPCnow Sites: | --- |
| HPE Sites: | --- | IBM Sites: | --- |
| NOAA SIte: | --- | OCF Sites: | --- |
| Recursion Pharma Sites: | --- | SFW Sites: | --- |
| SNIC sites: | --- | Linux Distro: | --- |
| Machine Name: | CLE Version: | ||
| Version Fixed: | 14.11.8 | Target Release: | --- |
| DevPrio: | --- | Emory-Cloud Sites: | --- |
Regular expression support was added in version 14.11 as I recall. I'll update that documentation. On June 4, 2015 5:42:45 PM PDT, bugs@schedmd.com wrote: >http://bugs.schedmd.com/show_bug.cgi?id=1724 > > Site: Stanford > Bug ID: 1724 > Summary: gres.conf File= option clarification > Product: Slurm > Version: 14.11.7 > Hardware: Linux > OS: Linux > Status: UNCONFIRMED > Severity: 4 - Minor Issue > Priority: --- > Component: Documentation > Assignee: brian@schedmd.com > Reporter: kilian@stanford.edu > CC: brian@schedmd.com, da@schedmd.com, david@schedmd.com, > jette@schedmd.com > >Hi there, > >I've re-read the man page for gres.conf and I'm confused. It says: > >-- 8< >---------------------------------------------------------------------- >File Fully qualified pathname of the device files associated with a >resource. The file name parsing logic does not include any support for >regular >expressions. Each file must be explicitly named, one per line. >-- 8< >---------------------------------------------------------------------- > >Yes, further down, the example seems contradictory: >-- 8< >---------------------------------------------------------------------- > ################################################################## > # SLURM's Generic Resource (GRES) configuration file > # Use a single gres.conf file for all compute nodes > ################################################################## > NodeName=tux[0-15] Name=gpu File=/dev/nvidia[0-3] > NodeName=tux[16-31] Name=gpu File=/dev/nvidia[0-7] >-- 8< >---------------------------------------------------------------------- > >So which one is it? One File= per line, or can they be regrouped as in >the >example? > >Thanks, >Kilian > >-- >You are receiving this mail because: >You are on the CC list for the bug. Documentation updated in this commit: https://github.com/SchedMD/slurm/commit/22b7f1adbe1e5a95264a26987c8ce09fa035ffab |
Hi there, I've re-read the man page for gres.conf and I'm confused. It says: -- 8< ---------------------------------------------------------------------- File Fully qualified pathname of the device files associated with a resource. The file name parsing logic does not include any support for regular expressions. Each file must be explicitly named, one per line. -- 8< ---------------------------------------------------------------------- Yes, further down, the example seems contradictory: -- 8< ---------------------------------------------------------------------- ################################################################## # SLURM's Generic Resource (GRES) configuration file # Use a single gres.conf file for all compute nodes ################################################################## NodeName=tux[0-15] Name=gpu File=/dev/nvidia[0-3] NodeName=tux[16-31] Name=gpu File=/dev/nvidia[0-7] -- 8< ---------------------------------------------------------------------- So which one is it? One File= per line, or can they be regrouped as in the example? Thanks, Kilian