Add milliseconds to default log message header (both RFC 5424 and ISO 8601
time formats). Disable milliseconds logging using the configure
parameter "--disable-log-time-msec". Default time format changes to
ISO 8601 (without time zone information). Specify "--enable-rfc5424time"
to restore the time zone information.

Add milliseconds to default log message header with the (default)
RFC5424 time format. Disable milliseconds logging using the configure
parameter "--enable-rfc5424time-secs". Sample time stamp format is as
follows: "2013-03-13T14:28:17.767-07:00".

Conflicts:
	doc/man/man1/sbatch.1

If step requests more CPUs than possible in specified node count of job
allocation then return ESLURM_TOO_MANY_REQUESTED_CPUS rather than
ESLURM_NODES_BUSY and retrying.

Conflicts:
	src/plugins/select/cons_res/select_cons_res.c

I found a bug in cons_res/select_p_select_nodeinfo_set_all.

If a node is part of two (or more) partitions the code will only count the number of cores/cpus in the partition that has the most running jobs on that node.

Patch attached to fix the problem.

I also added an new function to bitstring to count the number of bits in an range (bit_set_count_range) and made a minor improvement of (bit_set_count) while reviewing the range version.

Best regards,
Magnus

This permits default reservation names to be more easily managed

Without this change, when the sbatch --export option is used, many
Slurm environment variables are not set unless explicitly exported.

Hello,

Please find attached a patch with two fixes for init.d scripts:

* correct comments (full path to slurm binaries was not correct in comments);

* improve the output of 'service [slurm|slurmdbd] reconfig'.  It used
to garble the console because of the missing 'echo' after 'killproc'.
'[OK]' was displayed on the same line as the shell prompt in CentOS
6.4.  Now it looks correctly:

[root@head ~]# service slurm reconfig
Reloading slurmctld daemon configuration:                  [  OK  ]
[root@head ~]#

Please review and apply.

Dmitri

accounting.

Conflicts:
	META
	NEWS

Conflicts:
	NEWS
	doc/html/news.shtml

This problem would effect systems in which specific GRES are associated
with specific CPUs.
One possible result is the CPUs identified as usable could be inappropriate
and job would be held when trying to layout out the tasks on CPUs (all
done as part of the job allocation process).
The other problem is that if multiple GRES are linked to specific CPUs,
there was a CPU bitmap OR which should have been an AND, resulting in
some CPUs being identified as usable, but not available to all GRES.