That's great! Thank you very much! :)

Cheers


On Wed, Oct 16, 2013 at 6:33 PM, Moe Jette <[email protected]> wrote:

>
> Done (but in a different location):
>
> https://github.com/SchedMD/**slurm/commit/**c667a9952e6674b85289cb92c62fd5
> **b7bece9adf<https://github.com/SchedMD/slurm/commit/c667a9952e6674b85289cb92c62fd5b7bece9adf>
>
>
> Quoting Chrysovalantis Paschoulas <[email protected]>:
>
>  Dear developers,
>>
>> we have a small testing cluster with 44 compute nodes, the OS is
>> Scientific
>> Linux 6.4 and we are using SLURM. The first installed version of Slurm was
>> 2.5.7 and we have upgraded Slurm to 2.6.0 -> 2.6.1 -> 2.6.2 -> 2.6.3.
>>
>> We always build the Slurm packages. We download the sources from: "
>> http://www.schedmd.com/#repos"; and we build them with the command:
>> "rpmbuild -ta slurm*.tar.bz2".
>>
>> Always we had an issue with the init script "/etc/init.d/slurm". On the
>> compute nodes this script returns always that the slurmd daemon is not
>> running, even if it is. The problem lies in the slurmstatus() function
>> where the $pidfile variable has the special character '"' and it can never
>> test correctly if the pid file exists or not. In order to fix this
>> behaviour we add one command in the init script:
>>
>> line 167: pidfile=${pidfile//\"/}
>>
>> So, could you please include this fix in the next Slurm version 2.6.4?? It
>> could be also possible that the default init script has some other issues
>> that we haven't found yet, so it would be nice if you could check it more
>> deeply. Thanks in advance!
>>
>> Best Regards,
>> Chrysovalantis Paschoulas
>>
>> Juelich Supercomputing Centre
>> Forschungszentrum Juelich, Germany
>>
>>
>

Reply via email to