- Oct 12, 2010
-
-
Michael Hanselmann authored
These fields can help with debugging. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
- Aug 23, 2010
-
-
Michael Hanselmann authored
When removing the field in commit 9bdab621, I forgot to remove some parts. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
- Jun 09, 2010
-
-
Michael Hanselmann authored
- Update NEWS file - Remove dependency on OpenSSL (pyOpenSSL remains) - Update manpages, fix typos and other things Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
- Jun 01, 2010
-
-
Iustin Pop authored
Since the current start_timestamp opcode attribute refers to the inital start time, before locks are acquired, it's not useful to determine the actual execution order of two opcodes/jobs competing for the same lock. This patch adds a new field, exec_timestamp, that is updated when the opcode moves from OP_STATUS_WAITLOCK to OP_STATUS_RUNNING, thus allowing a clear view of the execution history. The new field is visible in the job output via the 'opexec' field. Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Guido Trotter <ultrotter@google.com>
-
- Oct 22, 2009
-
-
Michael Hanselmann authored
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>
-
- Sep 15, 2009
-
-
Michael Hanselmann authored
Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
- Sep 14, 2009
-
-
Guido Trotter authored
It currently reports "cancel" in its syntax, which is obviously a cut&paste error. Signed-off-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
- Sep 04, 2009
-
-
Michael Hanselmann authored
Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Luca Bigliardi <shammash@google.com>
-
- Aug 03, 2009
-
-
Michael Hanselmann authored
This command can be used to follow the output of a job. It's useful together with the --submit parameter for other commands. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
- Feb 12, 2009
-
-
Iustin Pop authored
This patch updates the gnt-* scripts to show the new 2.0 syntax. It's not guaranteed to be 80% complete. Reviewed-by: ultrotter
-