feature request: mxqkill

[arndt]

As a user I sometimes want to kill/cancel my jobs as fast as possible. Especially I do not want to look up a group id and type it into again. Why not have something like

mxqkill -all

which would kill all jobs which it can kill.

Note: mxqkill -u USER does not work for normal users.

[donald]

Sounds sensible. I would just opt for (-A | --all) instead of -all . This is not Java or tar but nice longopts :-)

[arndt]

even better - you may probably want disable this option for privileged users, or not - no risk no fun

[donald]

Hmmm. Is it better to kill the jobs or the groups or to have both options? If the later, -A | --all is not enough. But to map --all-jobs and --all-groups to short options is not straight forward.

--group-id maps to -g' but --job-idmaps to uppercase-J` (probably to mach mxqdump, don't remember).

Maybe like this:

mxqkill -A or mxqkill --all to kill all groups
mxqkill -Aj or mxqkill --all --jobs to kill all jobs

That would be in line with mxqdump.

Or just don't defined short options for --all-groups and --all-jobs ?

[pmenzel]

Is it better to kill the jobs or the groups or to have both options?

Please excuse my ignorance. What is the difference? Would “kill the job” mean to kill the running jobs?

[arndt]

Is one of these options faster than the other? Then I would opt for the fastest option to be mxqkill --all.

[donald]

Is it better to kill the jobs or the groups or to have both options?

Please excuse my ignorance. What is the difference? Would “kill the job” mean to kill the running jobs?

If the group is cancelled, the group goes into to the status 'CANCELLED' and is no longer open for new jobs. If you submit again with with same parameters, a new group would be created. This is more or less only a difference for the statistics.

As we only would cancel active (running or pending) jobs, we should also only cancel active groups (those with running or pending jobs), and not really all (historical) groups of the user.

Maybe we should just go for the jobs and not for the groups for now.

Is one of these options faster than the other? Then I would opt for the fastest option to be mxqkill --all.

All jobs is faster in theory only, but it shouldn't make a noticeable difference in the real world.

[arndt]

Maybe we should just go for the jobs and not for the groups for now.

Agreed

[donald]

btw: You can open mxq-related issue at https://github.molgen.mpg.de/mariux64/mxq/issues ,too. Next time :-)

[donald]

Go ahead an kill all your active jobs with mxqkill -A. Be aware, that this includes mxqi jobs.