On Tue, May 3, 2011 at 9:48 PM, Danny Auble <[email protected]> wrote: > Hi Stephan, > >> Hi, > >> > >> I have set AccountingStorage and JobComp to use MySQL (has I have not > >> found yet the slurmdbd interface for JobComp) and I wonder how could I > >> hide the AccountingStoragePass and JobCompPass attributes from the > >> user scope. > > Is there a reason you are using both AccountingStorage and JobComp? JobComp > is a subset of information sent to AccountingStorage, mostly duplicate > information, and only when jobs end. This is the reason there isn't a > JobComp/slurmdbd plugin. It wasn't envisioned one would use the slurmdbd to > house both. > > In the case of the slurmdbd the slurmdbd.conf file only needs to be readable > from the slurm user and root. Regular users don't need to read it, > authentication is usually done through munge. Without the slurmdbd there > currently isn't anyway to protect the passwords since they are needed for > sacct to communicate with the database. > > If possible I would revisit why you need both AccountingStorage and JobComp, > or you could write your own plugin to send JobComp data to the SlurmDBD. > >> Are all the attributes of slurmd.conf checked between slurmd and > >> slurmctld instances or is there attributes that can be changed without > >> having an output in syslog about differences ? > > I am guessing you mean slurm.conf instead of slurmd.conf. > > It is a wise move to keep the slurm.conf file in sync on all nodes, hence > the warning, the node addresses are used in the tree fanout slurm uses to > send/receive messages. > > If you don't want this warning (I would advise keeping your slurm.conf in > sync on all your nodes) you can disable it with > > DebugFlags=NO_CONF_HASH > > in your slurm.conf. > > Danny > >> > >> Regards, > >> > >> Stephan > >> > >
Perfect, thank you, this answered all my questions. -- Stéphan
