document:

• job hierarchy
• deadlock prevention
• job idempotence

Useful for job visualization and for other niceness distribution strategies, for example giving more priority to children processes, since parent might be waiting for them to finish

PeerChannel constructor may hang forever if client process terminates before its execution, producing a memory leak since thread is never finished

http://unix.stackexchange.com/questions/59300/how-to-place-store-a-file-in-memory-on-linux

refactor current project to create a java client project that allows interacting with the scheduler without creating a process

to ensure that notified listeners read the file once it's completely written

Both por input and output

Add this option to group and job listing to easy parsing. Disable ANSI colors in this case

http://unix.stackexchange.com/questions/305606/linux-inactive-memory/305752#305752

use -j for a job submenu, just as it's done for groups

• plugin implementation
• predefined groups

Several deadlock scenarios can occur:

1. Submitted job with excessive RSS promise (and schedulerCfg.maxJobRSSBytes=-1)
2. Submitted child job (job launched by other job that waits for it) and the sum of the promises from the root ancestor to it exceeding schedulerCfg.maxTotalRSSBytes
3. All running jobs waiting for queued jobs to end

The two first are irresolvable scenarios, so submission should fail.

The last one can be addressed in different ways.

• Making the scheduler preemptive, so running jobs could be stopped for later execution. A way of freezing a process is needed for this. This would allow to freeze a process to make room to other process descendants (not its own descendants)
• Canceling running jobs, maybe introducing the concept of job idempotence for later relaunching

I followed the instructions to install and start wava on Ubuntu Server 18.04 but when I start the service with:
sudo systemctl start wava.service
I got the error:
Job for wava.service failed because a timeout was exceeded.

How can I solve it?