*nix Documentation Project
·  Home
 +   man pages
·  Linux HOWTOs
·  FreeBSD Tips
·  *niX Forums

  man pages->OpenBSD man pages -> sendbug (1)              
Title
Content
Arch
Section
 

SENDBUG(1)

Contents


NAME    [Toc]    [Back]

     sendbug - report a bug in OpenBSD

SYNOPSIS    [Toc]    [Back]

     sendbug [-LPV] [--version]

DESCRIPTION    [Toc]    [Back]

     sendbug is a tool used to submit problem  reports  (PRs)  to
the OpenBSD
     bugs  database.   sendbug invokes an editor on a problem report template
     (after filling in some fields with reasonable  default  values).  When you
     exit  the  editor,  sendbug  sends the completed form to the
OpenBSD bugs
     database.  The PR will  be  assigned  a  unique  number  and
stored in the bugs
     database according to its category.  An automatic reply will
be sent with
     an acknowledgement, citing the category and the PR number.

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

     The more precise your problem description and the more  complete your information,
 the faster the OpenBSD team will be able to solve
your problem.


     The options are as follows:

     -L      Print the list of available categories.  No mail  is
sent.

     -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.

     -V      Display the sendbug version number.

     --version
             Same as -V.

     Note:  Use  sendbug  to  submit  problem reports rather than
mailing them directly.
  Using both the template  and  sendbug  itself  will
help ensure all
     necessary  information will reach the OpenBSD bugs database.

ENVIRONMENT    [Toc]    [Back]

     EDITOR   Specifies the editor to  invoke  on  the  template.
The default editor
 is /usr/bin/vi.

     PR_FORM   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    [Toc]    [Back]

     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 per 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  bugs  database
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  contents of the PR is not confidential; it is sent
out to a public
 mailing list.   Sensitive,  security-related  issues
should be sent
         via email to <[email protected]>.

HOW TO SUBMIT TEST CASES, CODE, ETC.
     Submit small code samples with the PR.  Contact <[email protected]> for
     instructions on submitting larger test cases and problematic
source code.

FILES    [Toc]    [Back]

     /tmp/p.XXXXXXXXXX     copy of PR used in editing session
     /tmp/pf.XXXXXXXXXX    copy of empty PR form (testing purposes)
     /tmp/pbad.XXXXXXXXXX  file for rejected PRs

AUTHORS    [Toc]    [Back]

     Jeffrey Osier, Brendan Kehoe, Jason Merrill, Heinz G.  Seidl
(Cygnus Support)

COPYING    [Toc]    [Back]

     Copyright (c) 1992, 1993 Free Software Foundation, Inc.

     Permission is granted to make and distribute verbatim copies
of this manual
 provided the copyright notice and this permission notice
are preserved
 on all copies.

     Permission  is  granted to copy and distribute modified versions of this
     manual under the conditions for verbatim  copying,  provided
that the entire
  resulting  derived work is distributed under the terms
of a permission
 notice identical to this one.

     Permission is granted to copy and distribute translations of
this manual
     into  another language, under the above conditions for modified versions,
     except that this permission notice may be included in translations approved
  by  the  Free  Software Foundation instead of in the
original English.


                               February         27,          2003
[ Back ]
 Similar pages
Name OS Title
release OpenBSD building an OpenBSD release
dhcp OpenBSD configuring OpenBSD for DHCP
mdoc.samples OpenBSD tutorial sampler for writing OpenBSD manuals
compat_aout OpenBSD setup for running a.out OpenBSD binaries on ELF systems
iostat OpenBSD report I/O statistics
bashbug Linux report a bug in bash
rpcinfo IRIX report RPC information
rpcinfo FreeBSD report RPC information
clock Tru64 Report CPU time used
iostat FreeBSD report I/O statistics
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service