From owner-cvs-all  Fri Jan 29 20:25:38 1999
Return-Path: <owner-cvs-all@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA11175
          for cvs-all-outgoing; Fri, 29 Jan 1999 20:25:38 -0800 (PST)
          (envelope-from owner-cvs-all@FreeBSD.ORG)
Received: from red.juniper.net (red.juniper.net [208.197.169.254])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA11168
          for <committers@freebsd.org>; Fri, 29 Jan 1999 20:25:37 -0800 (PST)
          (envelope-from pst@juniper.net)
Received: from base.juniper.net (base.juniper.net [208.197.169.208])
	by red.juniper.net (8.8.8/8.8.5) with ESMTP id UAA25336
	for <committers@freebsd.org>; Fri, 29 Jan 1999 20:25:35 -0800 (PST)
Received: (from pst@localhost) by base.juniper.net (8.9.2/8.7.3) id UAA00906 for committers@freebsd.org; Fri, 29 Jan 1999 20:25:35 -0800 (PST)
Date: Fri, 29 Jan 1999 20:25:35 -0800 (PST)
From: Paul Traina <pst@juniper.net>
Message-Id: <199901300425.UAA00906@base.juniper.net>
To: committers@FreeBSD.ORG
Subject: SCSI tagged openings message
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk

Why should we care?  This seems like a relatively useless syslog message
until the openings are exhausted and are somehow thrashing...?  Can this
be silenced or killed?


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