1SEND-PR(1) General Commands Manual SEND-PR(1)
2
6 ipsec send-pr - send problem report (PR) to a central support site
7
9 ipsec send-pr [ site ] [ -f problem-report ] [ -t mail-address ]
10 [ -P ] [ -L ] [ -s severity ] [ -c address ]
11 [ --request-id ] [ -V ]
12
14 ipsec send-pr is a tool used to submit problem reports (PRs) to a cen‐
15 tral support site. In most cases the correct site will be the default.
16 This argument indicates the support site which is responsible for the
17 category of problem involved. Some sites may use a local address as a
18 default. site values are defined by using the aliases(5).
19 ipsec send-pr invokes an editor on a problem report template (after
21 trying to fill in some fields with reasonable default values). When
22 you exit the editor, ipsec send-pr sends the completed form to the
23 Problem Report Management System (GNATS) at a central support site. At
24 the support site, the PR is assigned a unique number and is stored in
25 the GNATS database according to its category and submitter-id. GNATS
26 automatically replies with an acknowledgement, citing the category and
27 the PR number.
28 To ensure that a PR is handled promptly, it should contain your
30 (unique) submitter-id and one of the available categories to identify
31 the problem area. (Use `ipsec send-pr -L' to see a list of cate‐
32 gories.)
33 The ipsec send-pr template at your site should already be customized
35 with your submitter-id (running `install-sid submitter-id' to accom‐
36 plish this is part of the installation procedures for ipsecsend-pr).
37 If this hasn't been done, see your system administrator for your sub‐
38 mitter-id, or request one from your support site by invoking `ipsec
39 send-pr --request-id'. If your site does not distinguish between dif‐
40 ferent user sites, or if you are not affiliated with the support site,
41 use `net' for this field.
42 The more precise your problem description and the more complete your
44 information, the faster your support team can solve your problems.
45
47 -f problem-report
48 specify a file (problem-report) which already contains a com‐
49 plete problem report. ipsec send-pr sends the contents of the
50 file without invoking the editor. If the value for problem-
51 report is `-', then ipsec send-pr reads from standard input.
52 -s severity
54 Give the problem report the severity severity.
55 -t mail-address
57 Change mail address at the support site for problem reports.
58 The default mail-address is the address used for the default
59 site. Use the site argument rather than this option in nearly
60 all cases.
61 -c address
63 Put address in the Cc: header of the message.
64 -P print the form specified by the environment variable PR_FORM on
66 standard output. If PR_FORM is not set, print the standard
67 blank PR template. No mail is sent.
68 -L print the list of available categories. No mail is sent.
70 --request-id
72 sends mail to the default support site, or site if specified,
73 with a request for your submitter-id. If you are not affiliated
74 with site, use a submitter-id of net'.
75 -V Display the ipsec send-pr version number.
77 Note: use ipsec send-pr to submit problem reports rather than mailing
79 them directly. Using both the template and ipsec send-pr itself will
80 help ensure all necessary information will reach the support site.
81
83 The environment variable EDITOR specifies the editor to invoke on the
84 template.
85 default: vi
86 If the environment variable PR_FORM is set, then its value is used as
88 the file name of the template for your problem-report editing session.
89 You can use this to start with a partially completed form (for example,
90 a form with the identification fields already completed).
91
93 Problem reports have to be in a particular form so that a program can
94 easily manage them. Please remember the following guidelines:
95 · describe only one problem with each problem report.
97 · For follow-up mail, use the same subject line as the one in the
99 automatic acknowledgent. It consists of category, PR number and the
100 original synopsis line. This allows the support site to relate sev‐
101 eral mail messages to a particular PR and to record them automati‐
102 cally.
103 · Please try to be as accurate as possible in the subject and/or syn‐
105 opsis line.
106 · The subject and the synopsis line are not confidential. This is
108 because open-bugs lists are compiled from them. Avoid confidential
109 information there.
110 See the GNU Info file send-pr.info or the document Reporting Problems
112 With send-pr for detailed information on reporting problems
113
115 Submit small code samples with the PR. Contact the support site for
116 instructions on submitting larger test cases and problematic source
117 code.
118
120 /tmp/p$$ copy of PR used in editing session
121 /tmp/pf$$ copy of empty PR form, for testing purposes
122 /tmp/pbad$$ file for rejected PRs
123 @IPSEC_DIR@/send-pr.confscript to customize send-pr.
124
126 An Emacs user interface for send-pr with completion of field values is
127 part of the send-pr distribution (invoked with M-x send-pr). See the
128 file send-pr.info or the ASCII file INSTALL in the top level directory
129 of the distribution for configuration and installation information.
130 The Emacs LISP template file is send-pr-el.in and is installed as send-
131 pr.el.
132
134 See send-pr.info or INSTALL for installation instructions.
135
137 Reporting Problems Using send-pr (also installed as the GNU Info file
138 send-pr.info).
139 gnats(l), query-pr(1), edit-pr(1), gnats(8), queue-pr(8), at-pr(8),
141 mkcat(8), mkdist(8).
142
144 Jeffrey Osier, Brendan Kehoe, Jason Merrill, Heinz G. Seidl (Cygnus
145 Support)
146
148 Copyright (c) 1992, 1993 Free Software Foundation, Inc.
149 Permission is granted to make and distribute verbatim copies of this
151 manual provided the copyright notice and this permission notice are
152 preserved on all copies.
153 Permission is granted to copy and distribute modified versions of this
155 manual under the conditions for verbatim copying, provided that the
156 entire resulting derived work is distributed under the terms of a per‐
157 mission notice identical to this one.
158 Permission is granted to copy and distribute translations of this man‐
160 ual into another language, under the above conditions for modified ver‐
161 sions, except that this permission notice may be included in transla‐
162 tions approved by the Free Software Foundation instead of in the origi‐
163 nal English.
164February 1993 xVERSIONx SEND-PR(1)