SEND-PR (1) | General commands | Unix Manual Pages

SEND-PR (1) | General commands | Unix Manual Pages | :man▋

send-pr invokes an editor on a problem report template (after trying to fill in some fields with reasonable default values). When you exit the editor, send-pr sends the completed form to the Problem Report Management System (GNATS) at a central support site. At the support site, the PR is assigned a unique number and is stored in the GNATS database according to its category and submitter-id. GNATS automatically replies with an acknowledgement, citing the category and the PR number.

To ensure that a PR is handled promptly, it should contain one of the available categories to identify the problem area. (Use ‘send-pr -L’ to see a list of categories.)

The more precise your problem description and the more complete your information, the faster your support team can solve your problems.

send-pr depends on a correctly configured mail submission system to work correctly. If, for any reason, sending mail is not working, problem reports can be submitted over the web, through:

http://www.freebsd.org/send-pr.html

OPTIONS

-f" problem-report"
	specify a file (problem-report) which already contains a complete problem report. send-pr sends the contents of the file without invoking the editor. If the value for problem-report is ‘-’, then send-pr reads from standard input.
-s" severity"
	Give the problem report the severity severity.
-t" mail-address"
	Change mail address at the support site for problem reports. The default mail-address is the address used for the default site. Use the site argument rather than this option in nearly all cases.
-c" address"
	Put address in the Cc: header of the message.
-a" file"	Copy the specified file into the Fix: section. Binary files are uuencoded.
-P	print the form specified by the environment variable PR_FORM on standard output. If PR_FORM is not set, print the standard blank PR template. No mail is sent.
-L	print the list of available categories. No mail is sent.
-V	Display the send-pr version number. This may also be specified as --version.

Note: use send-pr to submit problem reports rather than mailing them directly. Using both the template and send-pr itself will help ensure all necessary information will reach the support site.

FREEBSD CATEGORIES

advocacy
	This used to be for the advocacy WWW pages. Now deprecated in favour of the www category, relevant alternative use of this category is encouraged.
alpha	Alpha processor specific problems.
amd64	AMD64 processor specific problems.
bin	Corrections or enhancements to system executables.
conf	Corrections or enhancements to the system configuration files.
docs	Corrections or enhancements to the manpages or other documentation.
gnu	Corrections or enhancements to the GNU contributed software.
i386	Intel x86 processor specific problems.
ia64	Intel ia64 processor specific problems.
java	Problems related to Java.
kern	Changes or enhancements to the architecture independent kernel sources.
misc	Problems that do not fit into any of the other categories.
ports	Corrections or enhancements (including new ports) to the ports collection.
powerpc
	PowerPC processor specific problems.
sparc64
	SPARC processor specific problems.
standards
	Standards conformance issues.
threads
	Problems related to threading on FreeBSD.
usb	Problems related to the USB subsystem.
www	Changes or enhancements to the FreeBSD website.

ENVIRONMENT

The environment variable EDITOR specifies the editor to invoke on the template.
default: vi

If the environment variable MAIL_AGENT is set, its value is used as the path + command line arguments of the executable to be invoked for sending the problem report (which will be provided via standard input).
This can be useful if you either use a MTA other than sendmail or need to provide additional parameters, such as the envelope sender on machines without a valid FQDN.
Default value: /usr/sbin/sendmail -oi -t

If the environment variable PR_FORM is set, then its value is used as the file name of the template for your problem-report editing session. You can use this to start with a partially completed form (for example, a form with the identification fields already completed).

"HOW TO FILL OUT A PROBLEM REPORT"

Problem reports have to be in a particular form so that a program can easily manage them. Please remember the following guidelines: -->

o	describe only one problem with each problem report.
o	For follow-up mail, use the same subject line as the one in the automatic acknowledgement. It consists of category, PR number and the original synopsis line. This allows the support site to relate several mail messages to a particular PR and to record them automatically.
o	Please try to be as accurate as possible in the subject and/or synopsis line.
o	The subject and the synopsis line are not confidential. This is because open-bugs lists are compiled from them. Avoid confidential information there.