History | View | Annotate | Download (7.8 kB)
Finalize removal of “lock_status” job field
When removing the field in commit 9bdab62198, I forgot to remove some parts.
Signed-off-by: Michael Hanselmann <hansmi@google.com>Reviewed-by: Iustin Pop <iustin@google.com>
Start to prepare documentation for 2.2 release
- Update NEWS file- Remove dependency on OpenSSL (pyOpenSSL remains)- Update manpages, fix typos and other things
Add a new opcode timestamp field
Since the current start_timestamp opcode attribute refers to the initalstart time, before locks are acquired, it's not useful to determine theactual execution order of two opcodes/jobs competing for the same lock.
This patch adds a new field, exec_timestamp, that is updated when the...
gnt-job manpage: Remove detailed description for lock_status
The format changed in the meantime and should be self-explanatory.
Signed-off-by: Michael Hanselmann <hansmi@google.com>Reviewed-by: Guido Trotter <ultrotter@google.com>
Export new lock_status field to gnt-job
Fix small error in gnt-job manpage
Signed-off-by: Michael Hanselmann <hansmi@google.com>Reviewed-by: Luca Bigliardi <shammash@google.com>
Add “gnt-job watch” command
This command can be used to follow the output of a job. It's usefultogether with the --submit parameter for other commands.
Update the command line scripts man pages for 2.0
This patch updates the gnt-* scripts to show the new 2.0 syntax. It'snot guaranteed to be 80% complete.
Reviewed-by: ultrotter