From owner-freebsd-bugs  Sun May  3 09:38:57 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA18669
          for freebsd-bugs-outgoing; Sun, 3 May 1998 09:38:57 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA18663
          for <freebsd-bugs@FreeBSD.org>; Sun, 3 May 1998 09:38:55 -0700 (PDT)
          (envelope-from rhh@ct.picker.com)
Received: from ct.picker.com by whqvax.picker.com with SMTP;
          Sun, 3 May 1998 12:35:25 -0400 (EDT)
Received: from elmer.ct.picker.com by ct.picker.com (4.1/SMI-4.1)
	id AA05848; Sun, 3 May 98 12:35:25 EDT
Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4)
	id MAA05058; Sun, 3 May 1998 12:35:20 -0400
Message-Id: <19980503123520.A5017@ct.picker.com>
Date: Sun, 3 May 1998 12:35:20 -0400
From: Randall Hopper <rhh@ct.picker.com>
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
Cc: freebsd-bugs@FreeBSD.ORG
Subject: Re: bin/5296
References: <19980503110644.A4917@ct.picker.com> <11530.894208509@critter.freebsd.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <11530.894208509@critter.freebsd.dk>; from Poul-Henning Kamp on Sun, May 03, 1998 at 05:15:09PM +0200
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Poul-Henning Kamp:
 |>Poul-Henning Kamp:
 |> |> |> |Synopsis: slattach fails creating pidfile with ioctl(TIOCSCTTY):
 |> |> |> |          Operation not permitted
 |> |> |> |
 |> |> |> |State-Changed-From-To: open-closed
 |> |> |> |State-Changed-By: phk
...
 |
 |closed means: "It will never happen if it hasn't happened by now.  There
 |is no patch, and it is dogwash priority for everybody to make one."

Ok, now I know.  In the future I'll be less intent on investigating and
logging detailed PRs for bugs in less trafficed areas since they could just
be closed.

This is different from the style of bug tracking I'm used to.  That is, if
the bug is low enough priority it hasn't bubbled to the top, fine.  But it
still stays in the database until its fixed or the software is removed.

This open PR state info is useful for record keeping and searches.  For
example, if someone decides to rewrite or rework a software enditem, they
would certainly like to know the full set of open problems exist on that
software.  Or if someone is looking for an area to contribute that'll make
the biggest difference, they might like to see how many PRs are outstanding
on the candidate enditems.

 |Why don't you take a stab at fixing it yourself ?  If you send us a patch
 |bugs like this are likely to get fixed.

If it bubbles to the top of my priority, I will.  As a workaround, I just
ignore the PID file since it's existance can't be counted on so this isn't
too high a priority.

Randall

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message