NAME

mailbug − submit a bug report or enhancement request

SYNOPSIS

mailbug

DESCRIPTION

The mailbug utility allows users to submit machine-readable bug reports to the customer service representative for a Sequent system.  This service will be useful only if the customer service representative supports this method of problem tracking.  Check with your system administrator to ensure that the mailbug service is supported before submitting a bug report. 

Mailbug prompts for the information needed to fill out the bug report.  After the user has typed in all the required information, mailbug allows the user to inspect and edit the bug report before it is mailed, or to cancel the report completely.  Unless the report is canceled, mailbug sends a copy to the customer service representative and a copy to the user submitting the report.  Refer to the DYNIX System Administrator’s Guide for information on how to install the mailbug service. 

Mailbug will ask for the following information:

Your company or organization name, unless the file /usr/lib/mailbug_co_name exists.  /usr/lib/mailbug_co_name is a text file that might look like this:

Sequent Computer Systems, Inc
Department: New Product Introduction

Your full name and phone number, unless the file .mailbug exists in your home directory.  .mailbug is a text file that might look like this:

Anne Harris
Phone Number: 123-4567

A one-line summary of the bug. 

A full description of the bug, which may be as long as necessary. 

Which type of system the problem occurred on. 

An assessment of the severity of the bug.  The choices are:

Critical — an essential component of the hardware or operating system cannot be used. 

Serious — a non-essential module or utility cannot be used. 

Normal — some feature of a non-essential module or utility doesn’t work correctly, and there is no convenient workaround. 

Low — some feature of a non-essential module or utility doesn’t work correctly, but a user can work around the problem without serious inconvenience. 

Enhancement — suggestions on how the product can be improved. 

For Your Information — for information only, no action need necessarily be taken. 

A guess as to the source of the problem: documentation, hardware, mechanical, software, or other. 

For documentation problems, mailbug will prompt for the name of the manual involved, the page numbers, and the Rev numbers at the bottom of the pages. 

For hardware and mechanical bugs, mailbug will prompt for the type of hardware component (e.g., MULTIBUS disk controller board, peripheral mounting tower), and its part number, revision number, and serial number. 

For software bugs, mailbug will prompt for the pathname of the file(s) that the user suspects are incorrect — e.g., “/usr/ucb/man.”

If the requested information is unknown or is not applicable, some fields can be skipped by simply typing <CR> in response to the prompt. 

SEE ALSO

uucp(1)
DYNIX System Administrator’s Guide

DYNIX