Erica,

sure it could be changed. But then you have to change all the permissions of the different folders that slurm uses to reflect that.

Running daemons as root is discouraged since a few years for security reasons. This doesn't necessarly mean that the daemon is started by that user account but that it gives up all those privileges that it doesn't need right after the start and that it also changes the EUID (effective user id) once it did setup all the things it needs root privileges for (like binding a socket <1024). The keyword to search for is "capabilities". A very good and detailed book about this and many other topics is "The Linux Programming Interface" by Michael Kerrisk (http://man7.org/tlpi/)

Can you tell us how you installed slurm? Did you compile it yourself or used RPMs? If you used RPMs, those should have created the user account I was referring to.

I didn't have problems installing by following http://slurm.schedmd.com/quickstart_admin.html

Regards,

    Uwe


Am 05.08.2014 22:20, schrieb Erica Riello:
Re: [slurm-dev] Re: Re:
Hi Uwe,

I thought it could be changed to another user. Well, if it is the user who will run the daemons, shouldn't it be root?

Regards,

Erica


2014-08-05 17:10 GMT-03:00 Uwe Sauter <[email protected] <mailto:[email protected]>>:

    Hi Erica,

    I think you misunderstood the concept of "service user" in Linux.

    SlurmUser in the slurm.conf doesn't mean which user should be able
    to use SLURM (submit jobs, etc.) but which system user will run
    the slurm control daemon and slurm database daemon. This user is
    usually called "slurm".

    Here's the line of my /etc/passwd for this user:

    slurm:x:222:222:SLURM Manager:/:/bin/false


    Regards,

        Uwe


    Am 05.08.2014 22:04, schrieb Erica Riello:
    Kiran,

    that's exactly what I've done, but I still get the same error
    messages.

    Erica


    2014-08-05 15:54 GMT-03:00 Kiran Thyagaraja <[email protected]
    <mailto:[email protected]>>:


        You should be ideally specifying a directory under /var/spool
        e.g /var/spool/slurm and then change its permissions so that the
        SlurmUser can write to it.

        Kiran

        On 08/05/2014 01:33 PM, Mike Johnson wrote:

            Re: [slurm-dev]

            Hi Erica

            What's the value of SlurmUser in the slurm.conf?

            You'll need to make sure the MailProg exists and is
            executable by the SlurmUser too

            Mike


            On 5 August 2014 18:20, Erica Riello
            <[email protected] <mailto:[email protected]>
            <mailto:[email protected]
            <mailto:[email protected]>>> wrote:

                Hi all,

                I've been trying to run the slurm controller daemon,
            but I get an
                error I have no idea how to solve:

                > sudo slurmctld -Dcvvvv
                slurmctld: pidfile not locked, assuming no running daemon
                slurmctld: error: Configured MailProg is invalid
                slurmctld: error: Job accounting information
            gathered, but not stored
                slurmctld: fatal: Incorrect permissions on state save
            loc: /var/spool


                Munge daemon is running and /var/spool permissions are:

                > ls -ld /var/spool
                drwxr-xr-x 10 root root 4096 Ago  5 13:31 /var/spool

                Does anyone knows how should /var/spool permissions
            be set?

                Thanks in advance.

                -- Erica





-- ===============
    Erica Riello
    Aluna Engenharia de Computação PUC-Rio





--
===============
Erica Riello
Aluna Engenharia de Computação PUC-Rio


Reply via email to