if no home directory, log into '/'; delete old #ifdef/notdef and
[unix-history] / usr / src / libexec / bugfiler / bugfiler.8
... / ...
CommitLineData
1.\" Copyright (c) 1983 The Regents of the University of California.
2.\" All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms are permitted
5.\" provided that the above copyright notice and this paragraph are
6.\" duplicated in all such forms and that any documentation,
7.\" advertising materials, and other materials related to such
8.\" distribution and use acknowledge that the software was developed
9.\" by the University of California, Berkeley. The name of the
10.\" University may not be used to endorse or promote products derived
11.\" from this software without specific prior written permission.
12.\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR
13.\" IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
14.\" WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.
15.\"
16.\" @(#)bugfiler.8 6.9 (Berkeley) %G%
17.\"
18.TH BUGFILER 8 ""
19.UC 5
20.SH NAME
21bugfiler \- file bug reports in folders automatically
22.SH SYNOPSIS
23.B bugfiler
24[ -ar ] [-v version]
25.SH DESCRIPTION
26\fIBugfiler\fP is a program to automatically intercept, acknowledge,
27redistribute and store bug reports. \fIBugfiler\fP is normally invoked
28by the mail delivery program with a line similar to the following in
29/usr/lib/aliases.
30.PP
31.DT
32 bugs: "|bugfiler"
33.br
34.PP
35It should be noted that the login ``bugs'' must exist for the bugfiler
36to run. Unless otherwise noted all paths used by \fIbugfiler\fP are
37relative to the home directory of this login. \fIBugfiler\fP also
38expects all of its files and directories to be owned by ``bugs''.
39.PP
40For the bug report to be correctly filed, it must contain a line
41in the following format:
42.PP
43.DT
44 Index: \fIfolder\fP \fIversion\fP
45.br
46.PP
47The directories ~bugs/\fIversion\fP and ~bugs/\fIversion\fP/\fIfolder\fP
48must exist before \fIbugfiler\fP attempts to store the bug report. Bug
49reports will be stored in files named by the concatenation of \fIversion,
50folder,\fP and sequential numbers, i.e. if \fIversion\fP is ``4.3BSD'' and
51\fIfolder\fP is ``ucb'' the first bug report will be placed in
52~bugs/4.3BSD/ucb/1. If \fIfolder\fP contains more than one component only
53the first one will be used, e.g. if \fIfolder\fP is ``bin/from.c'' or
54``bin/adb/con.c'' it will be treated as if it were simply ``bin''. The
55\fI-v\fP flag is provided as a means to override the \fIversion\fP
56provided within the bug report itself.
57.PP
58A mail acknowledgement is automatically sent to the bug report filer unless
59the \fB-a\fP flag is supplied. The file ~bugs/\fIversion\fP/bug:ack is
60appended to this acknowledgement.
61.PP
62If the \fB-r\fP flag is not supplied, redistribution of the bug reports
63is done as specified in the file ~bugs/\fIversion\fP/bug:redist. This file
64is in the format of the \fIaliases\fP(5) file, including comments and
65entries requiring multiple lines, with the single exception that the
66\fIfolder\fP component of the ``Index:'' line replaces the name to alias.
67The special folder ``all:'' receives a redistribution of all bug reports
68sent to this \fIversion\fP. For example, the \fIbug:redist\fP file
69.PP
70.DT
71 # bigbug gets a copy of everything
72.br
73 all: bigbug
74.br
75 # ucb folder redistribution list
76.br
77 ucb: karels, kjd@coke.berkeley.edu
78.br
79 ra@beno.css.gov
80.br
81.PP
82will send copies of all bug reports with ``ucb'' as the \fIfolder\fP
83to bigbug, karels, kjd, and ra.
84.PP
85Reports that cannot be filed, due to an invalid ``Index:'' line or
86some other error, are placed in the directory ~bugs/errors. The
87\fIbugfiler\fP maintainer should correct these bug reports and then
88run \fIbugfiler\fP, with the corrected report as its standard input,
89as bug reports with errors are neither acknowledged or redistributed.
90All reports that \fIbugfiler\fP handles are logged in ~bugs/log.
91.PP
92Valid bugs are also logged in the file ~bugs/\fIversion\fP/summary.
93This file has an entry for each bug report for \fIversion\fP in the
94format:
95.PP
96.DT
97 Filename Date
98.br
99 Subject:
100.br
101 Index:
102.br
103 Owner: Bugs Bunny
104.br
105 Status: Received
106.br
107.PP
108\fIFilename\fP is the concatenation of \fIversion, folder,\fP and a number
109as described above. \fIDate\fP is the date as reported by the system
110clock, using ctime(3). The \fISubject:\fP and \fIIndex:\fP lines are
111copies of the ``Subject:'' and ``Index:'' lines contained in the bug
112report. The \fIOwner\fP and \fIStatus\fP fields are intended to provide a
113rudimentary method of tracking the status of bug reports.
114.PP
115The file ~bugs/bug:lock is the focus of all locking for \fIbugfiler.\fP
116If you wish to manipulate any of the log or error files, rename or remove
117it and \fIbugfiler\fP will treat all bug reports that it receives as if
118they were incorrectly formatted, i.e. it will place them in the directory
119~bugs/errors, for later recovery by the \fIbugfiler\fP maintainer.
120Obviously, this file must be created when you first install \fIbugfiler\fP.
121.PP
122All errors that occur before ~bugs/log is found are logged into the system
123log file, using
124.IR syslog (8).
125.SH FILES
126.br
127.TP 25
128~bugs/bug:ack
129the acknowledgement message
130.TP 25
131~bugs/bug:redist
132the redistribution list
133.TP 25
134~bugs/bug:lock
135the locking file
136.TP 25
137~bugs/errors/BUG_??????
138bug reports with format errors
139.TP 25
140~bugs/log
141the log file
142.TP 25
143~bugs/folder/summary
144the summary files
145.TP 25
146/usr/lib/sendmail
147the mail delivery program
148.TP 25
149/usr/lib/bugformat
150a sample bug report format
151.SH "SEE ALSO"
152sendbug(1), aliases(5), syslog(8)
153.SH BUGS
154Since mail can be forwarded in a number of different ways, \fIbugfiler\fP
155does not recognize forwarded mail and will acknowledge to the forwarder
156instead of the original sender unless there is a `Reply-To' field in the
157header.
158.PP
159This version of the bugfiler is not compatible with the version
160released with 4.3BSD in that it doesn't complain to the sender about
161incorrectly formatted bug reports.
162Frankly, we got tired of the profanity, not to mention the extended
163conversations
164.I bugfiler
165was holding with
166.IR vacation (1).