Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
The ONE Campaign to make poverty history

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

Who's Online
There are currently, 72 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here




       cvsbug [ site ] [ -f problem-report ] [ -t mail-address ]
               [ -P ] [ -L ] [ --request-id ] [ -v ]


       cvsbug is a tool used to submit problem reports (PRs) to a
       central support site.  In most cases the correct site will
       be the default.  This argument indicates the support  site
       which is responsible for the category of problem involved.
       Some sites may use a local address  as  a  default.   site
       values are defined by using the aliases(5).

       cvsbug  invokes  an  editor  on  a problem report template
       (after trying to  fill  in  some  fields  with  reasonable
       default  values).   When you exit the editor, cvsbug 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,  cit­
       ing the category and the PR number.

       To ensure that a PR is handled promptly, it should contain
       your (unique) submitter-id and one of the available  cate­
       gories  to identify the problem area.  (Use `cvsbug -L' to
       see a list of categories.)

       The cvsbug template at your site should  already  be  cus­
       tomized  with your submitter-id (running `install-sid sub­
       mitter-id' to accomplish this is part of the  installation
       procedures  for  cvsbug).   If  this hasn't been done, see
       your  system  administrator  for  your  submitter-id,   or
       request  one  from  your  support site by invoking `cvsbug
       --request-id'.  If your site does not distinguish  between
       different  user  sites,  or if you are not affiliated with
       the support site, use `net' for this field.

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


       -f problem-report
              specify a file (problem-report) which already  con­
              tains  a complete problem report.  cvsbug sends the
              contents of the file without invoking  the  editor.
              If the value for problem-report is `-', then cvsbug
              reads from standard input.

       -t mail-address
              Change mail address at the support site for problem
              specified, with a request  for  your  submitter-id.
              If  you are not affiliated with site, use a submit­
              ter-id of net'.

       -v     Display the cvsbug version number.

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


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

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


       Problem reports have to be in a particular form so that  a
       program  can easily manage them.  Please remember the fol­
       lowing guidelines:

       ·  describe only one problem with each problem report.

       ·  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 automat­

       ·  Please try to be as accurate as possible in the subject
          and/or synopsis line.

       ·  The subject and the synopsis line are not confidential.
          This is because open-bugs lists are compiled from them.
          Avoid confidential information there.

       See the GNU Info file cvsbug.info or the document  Report­
       ing  Problems  With  cvsbug for  detailed  information  on
       reporting problems


       Submit small code samples with the PR.  Contact  the  sup­
       port site for instructions on submitting larger test cases
       and problematic source code.


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


       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 ver­
       sions  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 con­
       ditions for modified versions, except that this permission
       notice  may  be  included  in translations approved by the
       Free  Software  Foundation  instead  of  in  the  original

February 1993               xVERSIONx                   CVSBUG(8)

An undefined database error occurred. SELECT distinct pages.pagepath,pages.pageid FROM pages, page2command WHERE pages.pageid = page2command.pageid AND commandid =

Show your Support for the Linux Tutorial

Purchase one of the products from our new online shop. For each product you purchase, the Linux Tutorial gets a portion of the proceeds to help keep us going.



Security Code
Security Code
Type Security Code

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!

Amazon Wish List

Did You Know?
The Linux Tutorial can use your help.


Tell a Friend About Us

Bookmark and Share

Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.09 Seconds