sandbox-top

Name

sandbox-top – display Sandbox tasks

Synopsis

sandbox-top [-h] [--log-path LOG_PATH]
               [--xml-rpc-url URL | --host HOST] [--show-childs]
               [--hide-hidden] [--task-type TASK_TYPE] [--owner USERNAME]
               [--statuses STATUS [STATUS ...]] [--interval SECONDS]
               [--layout LAYOUT_STRING] [--force-start]
               [--version | --list-task-types]

Description

The sandbox-top program provides a dynamic view of a running Sandbox. It can display a list of tasks being managed by the Sandbox. The order and size of information displayed for tasks are all user configurable.

Overview

Documentation

  1. Command-Line Options
  2. Columns

    a. Description of Fields

    b. Selecting and Ordering Columns

    c. Layout Examples

  3. Bugs

Operation

When operating sandbox-top, the most useful key is quit (q) key. Alternatively, you could simply use the traditional interrupt key (^C) when you are done.

1. Command-Line Options

2. Columns

2a. Description of Fields

Listed below are sandbox-top's available fields.

ID

The task's unique ID.

TYPE

The type of the task.

PRIO

The priority of the task.

H

The "hidden" flag:

S

The status of the task which can be of:

TIME

This column shows the task execution time if the task is executing, and the lifetime of the task (which is, in fact, the time in queue) otherwise.

DESCRIPTION

This column shows the description of the task.

MODEL

This column shows the CPU model of the client that executes the task.

HOST

This column shows the host name of the client that executes the task.

ARCH

This column shows the OS name of the client that executes the task.

2b. Selecting and Ordering Columns

The layout string specifies the order and size of columns. The format of layout string is:

layout ::= column[ column[ column[ ...]]]
column ::= column_name[align][width]
align ::= <|>|^

Column names is described above in the Columns section.

Align can be of:

Width can be of:

2c. Layout Examples

3. Bugs

Send bug reports to: Pavel Perestoronin, eigenein@yandex-team.ru

The file is generated with setup.py readme.