DA Task Manager

[vivalafe]

I think a very useful feature missing in Direct Admin is a Task Manager to handle or even cancel queue tasks running in the background or just watch its progress.
I have many times found my self in the situation of request, for example, a backup (put in queue) and latter figured out that I should have excluded a particular user. Or maybe you want to know how much time o percentage remains for the execution of a task in order to start another resource intensive one.
Do you agree?

 

[scsi]

I am sure a task monitor could happen, but task killer would cause a ton of problems.

 

[zEitEr]

I'd agree with vivalafe for that part that monitor would be useful as it would allow us to understand very quickly what exactly dataskq is doing in the current moment. And agree with scsi about problems with using a task killer.

 

[nobaloney]

I'm trying to understand the scope of this request. The example given by vivalafe, for example, a backup, is close to impossible to follow. Sure we could find out which backup is being run at the moment, and whether files are being found and gathered, or made into the tarball, or being transferred, but that wouldn't tell us what has already been done, or how much is left to do.

And if Directadmin created a new logging system to tell us what's already been done, it still would give us no idea as to how much time would be taken by what's still to be done.

As far as a task-killer is concerned, the main problem is that the backup task is really a series of many other tasks, which are being run in a specific order. For example, have you tried, for example, manually killing a tarball creation task as part of a backup? As soon as it's killed a new on starts up on another user.

So the key would be the understanding of the metatask and where the information is being stored.

So is it specifically the backup task or the restore task in which you're interested, or which other tasks? Or in other words, what's the scope of this request?

Jeff