Diabolical Dog.7

Fixed #165

Diabolical Dog.6

• Fixed: Wrong exit status of mxqkill
• Fixed (hopefully): Finished jobs not changing to FINISHED due to mysql deadlock

Diabolical Dog.5

mxqkill has new -A | --all option to cancel all active jobs of a user

Diabolical Dog.4

• mxqd_control: Check prerequisites against empty group tags

We want to be able to use group tags as a stigma so that servers can be
configured to accept only jobs without certain tags. For example,
mxqi can add a tag "mxqi" to its jobs and the servers which shouldn't
run mxqi jobs can use "!mxqi" as their prerequisites.

However, for that to work, we need to evaluate server prerequistes even
for jobs which don't have any tags.

Remove the check, which skips server prerequistes evaluation for jobs
without tags.

• mxqsub: Remove a stray space character from output
• mxqd_control: Check prerequisites against empty group tags

Diabolical Dog.3

• mxqsub: Implement --tmpdir argument without units

Diabolical Dog.2

• Don't fail on mxqub --umask 0
• Improve "Job with 123 has no ..." error message
• Add temporary gpu setup debug messages
• Fix potential gpu-init job-release race
• Fix bison build warning
• Better handle terminating jobs when /var/spool is full
• Use explicit character sets for database tables
• Create two indexes to reduces database load
• Remove message if -t is defaulted when using mxqsub
• Improve mxqkill usage message
• Avoid an assertion failure when database connection is lost temporarily

Diabolical Dog.1

• Fix "Groups job counts wrong after group is killed" (#154)

Diabolical Dog

mxqkill -J xxx can now be used to kill running jobs.

Chaotic Chameleon.9

• Don't let server go into WAITING state for unreasonable TMPDIR space requests

Chaotic Chameleon.8

• Avoid writeback of tmpdir when it is cleaned up after job completion.