- 19 Mar, 2013 5 commits
-
-
Morris Jette authored
-
Morris Jette authored
I don't believe save_time_limit was redundant. At least in this case: if (qos_ptr && (qos_ptr->flags & QOS_FLAG_NO_RESERVE)){ if (orig_time_limit == NO_VAL) orig_time_limit = comp_time_limit; job_ptr->time_limit = orig_time_limit; [...] So later, when updating the db, if (save_time_limit != job_ptr->time_limit) jobacct_storage_g_job_start(acct_db_conn, job_ptr); will cause the db to be updated, while, if (orig_time_limit != job_ptr->time_limit) jobacct_storage_g_job_start(acct_db_conn, job_ptr); will not because job_ptr->time_limit now equals orig_time_limit.
-
Morris Jette authored
Conflicts: src/db_api/cluster_report_functions.c src/plugins/sched/backfill/backfill.c
-
Morris Jette authored
-
Don Lipari authored
Without this change, if the job's time limit is modified down toward --time-min by the backfill scheduler, update the job's time limit in the database.
-
- 18 Mar, 2013 1 commit
-
-
Morris Jette authored
-
- 14 Mar, 2013 7 commits
-
-
Danny Auble authored
-
Morris Jette authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Morris Jette authored
-
Morris Jette authored
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.
-
- 13 Mar, 2013 8 commits
-
-
Morris Jette authored
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".
-
David Bigagli authored
-
Morris Jette authored
Conflicts: doc/man/man1/sbatch.1
-
Morris Jette authored
-
Morris Jette authored
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.
-
Morris Jette authored
-
Danny Auble authored
-
Danny Auble authored
-
- 12 Mar, 2013 3 commits
-
-
Morris Jette authored
Conflicts: src/plugins/select/cons_res/select_cons_res.c
-
Morris Jette authored
-
Magnus Jonsson authored
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
-
- 11 Mar, 2013 16 commits
-
-
Morris Jette authored
-
Morris Jette authored
This permits default reservation names to be more easily managed
-
Andy Wettstein authored
-
Nathan Yee authored
Without this change, when the sbatch --export option is used, many Slurm environment variables are not set unless explicitly exported.
-
Dmitri Gribenko authored
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
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
accounting.
-
Morris Jette authored
-
jette authored
-
jette authored
-
Morris Jette authored
-
jimmycao authored
-
jimmycao authored
-
jette authored
-