blob: 9ae536bdf5ddbb9086d5d9b1c83e994a766b729d (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
|
abrt-retrace-client(1)
======================
NAME
----
abrt-retrace-client - Handles the communication with Retrace server.
SYNOPSIS
--------
'abrt-retrace-client' <operation> [options]
DESCRIPTION
-----------
This tool is able to comunicate with Retrace server: create a new task,
ask about task's status, download log or backtrace of a finished task.
Integration with ABRT events
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'abrt-retrace-client' can be used as an analyzer for
application crashes which dump core.
Example usage in abrt_event.conf:
------------
EVENT=analyze analyzer=CCpp
abrt-retrace-client
------------
OPERATIONS
----------
create::
Creates a new task. Prints task ID and password to stdout.
Either -d or -c is required.
status::
Prints task\'s status to stdout. Both -t and -p are required.
log::
Prints finished task\'s log to stdout. Both -t and -p are required.
backtrace::
Print finished task\'s backtrace to stdout. Both -t and -p are required.
batch::
Runs all operations in one step: creates a new task, periodically
asks for status and downloads the result when finished. If the task
was successful, backtrace file is saved, otherwise log is printed
to stdout. Either -c or -d is required.
OPTIONS
-------
-v, --verbose::
be verbose
-s, --syslog::
log to syslog
-k, --insecure::
allow insecure connection to retrace server
--url URL::
retrace server URL
--headers::
(debug) show received HTTP headers
-d, --dir DIR::
read data from ABRT crash dump directory
-c, --core COREDUMP::
read data from coredump
--no-unlink::
(debug) do not delete temporary archive created in /tmp
-t, --task ID::
ID of the task on server
-p, --password PWD::
password of the task on server
AUTHORS
-------
* ABRT team
|