Moe, Thank you. I have been using these. I was wondering about the raw usage from the sshare command line tool.
The best I could get was. assoc_mgr_association_usage_t *usage; in the slurmdb_association_rec_t. All my queries resulted in this structure being NULL. Is there anyway to get this structure populated, because I believe the values may be in this structure. There is some typedef on the top of that header file, and I am unsure of this. Thanks, Andrew. On Wed, Dec 12, 2012 at 11:23:03AM -0700, Moe Jette wrote: > > The slurm commands use slurm APIs that are documented with man pages > (most of them anyway) and available for your direct use in case you > want to write your own tools. The header files are installed > slurm/slurm.h and slurm/slurmdb.h > > Quoting Andrew Carton <[email protected]>: > > > > > Hi slurm people, > > > > Mostly, up until now I was relying on the interface and the model > > defined in the public slurmdb and slurm header files that are > > installed on a system, and one can just link against them to use > > slurm. > > > > However, the sshare slurm command line tool, does something more > > interesting than the other command line tools. It appears to use an > > internal messaging / protocol that operates between the slurm > > controller and the slurm daemon. > > > > I would like to get share information but there is no public C > > interface defined that allows me to do this? Is this true? I am > > using slurm 2.4.3. > > > > > > I was wondering has that protocol been defined and would it be much > > effort to write a small standalone piece of C code that could query > > the current environment, lookup the slurm controller address and > > then send and receive a message to it, and then terminate. Does > > slurm communicate through sockets? I guess I would need to use munge > > too? Is there a library for that? > > > > Thanks, > > Andrew. >
