Hi Phil,
assuming that all sites maintaining their own Slurm rpm packages must
now somehow ensure that these are not replaced by the EPEL packages
anyway, why wouldn't it be possible, in the long run, to follow the
Fedora packaging guidelines for renaming existing packages?
https://docs.fedo
Hi Zainul,
there seems to be a hostname problem, your node is called "smaster" as far a I can see,
the slurmdbd log complains about the server host "smater".
Best
Marcus
Am 02.02.2021 um 14:05 schrieb Zainul Abiddin:
Hi All,
I have done slurmdbd configuration and while i am trying to run acco
Wow,
This is getting so ridiculous that my email program has started putting
this thread in junk...
The spirit of Linux is to give you the tools so you can do things how
you want. You have the tools, do not expect someone else to come over
and plant/maintain your garden. Just because they ca
On 2021-02-03 10:32, Brian Andrus wrote:
Wow,
This is getting so ridiculous that my email program has started
putting this thread in junk...
The spirit of Linux is to give you the tools so you can do things how
you want. You have the tools, do not expect someone else to come over
and plan
Hah, sigh yes that would be just fine ... *blushes*. Thanks! __
Best,
Chris
--
Christopher Coffey
High-Performance Computing
Northern Arizona University
928-523-1167
On 1/21/21, 11:10 PM, "slurm-users on behalf of Marcus Wagner"
wrote:
Hi Christopher,
doesn't it suffice to us
My main point here is that essentially upgrading someone from, for example,
SLURM 20.02 to SLURM 20.11 is not desirable, and that’s why upgrades between
major versions, IMO, should not happen automatically. There’s a whole section
of the documentation about how to do this properly, and I’m not s
On Wednesday, 03 February 2021, at 18:06:27 (+),
Philip Kovacs wrote:
> I am familiar with the package rename process and it would not have
> the effect you might think it would.If I provide an upgrade path to
> a new package name, e.g. slurm-xxx, the net effect would be to tell
> yum ordnf-ma
I am familiar with the package rename process and it would not have the effect
you might think it would.If I provide an upgrade path to a new package name,
e.g. slurm-xxx, the net effect would be to tell yum ordnf-managed systems that
the new package name for slurm is slurm-xxx. That would make
What you are describing is implemented in the EL ecosystems as module streams.
Streams are setup by maintainersto correspond to major version trains of
software. Users can then select the stream they want and can change streamsas
desired (unfortunately this is often not trivial), without upgra
