Peixin, Again, depends on your OS and deployment methods, but essentially:
In slurm.conf set SlurmctldPidFile=/var/run/slurmctld.pid SlurmdPidFile=/var/run/slurmd.pid SlurmdSpoolDir=/var/spool/slurmd SlurmUser=slurm SlurmctldLogFile=/var/log/slurm/slurm-ctld.log SlurmdLogFile=/var/log/slurm/slurm-d.log etc etc - note that these paths could be anything you want Then, during your set up (ie, once, when first installing OS) you need to: sudo mkdir /var/log/slurm sudo chown slurm /var/log/slurm sudo mkdir /var/spool/slurmd sudo chown slurm /var/spool/slurm and I personally have both set to 755, (owner read/write/execute; group and other read/execute) sudo chmod 755 /var/log/slurm sudo chmod 755 /var/spool/slurm cheers L. ------ The most dangerous phrase in the language is, "We've always done it this way." - Grace Hopper On 8 November 2016 at 08:25, Peixin Qiao <pq...@hawk.iit.edu> wrote: > Hi, > > When I make slurm.conf, I am confused about the following note: > > NOTE: The parent directories for Slurm's log files, process ID files, > state save directories, etc. are not created by Slurm. They must be created > and made writable by *SlurmUser* as needed prior to starting Slurm > daemons. > > How to make these files in detail? > > Best Regards, > Peixin >
