From owner-freebsd-bugs@FreeBSD.ORG  Mon Nov 10 21:47:16 2014
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 4D4F42D6
 for <freebsd-bugs@FreeBSD.org>; Mon, 10 Nov 2014 21:47:16 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 3670BFDB
 for <freebsd-bugs@FreeBSD.org>; Mon, 10 Nov 2014 21:47:16 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sAALlGKi079181
 for <freebsd-bugs@FreeBSD.org>; Mon, 10 Nov 2014 21:47:16 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 194935] New: pfctl(8) remove No ALTQ warning message
Date: Mon, 10 Nov 2014 21:47:16 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: 10.0-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: lyndon@orthanc.ca
X-Bugzilla-Status: Needs Triage
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
 op_sys bug_status bug_severity priority component assigned_to reporter
Message-ID: <bug-194935-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Nov 2014 21:47:16 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194935

            Bug ID: 194935
           Summary: pfctl(8) remove No ALTQ warning message
           Product: Base System
           Version: 10.0-RELEASE
          Hardware: Any
                OS: Any
            Status: Needs Triage
          Severity: Affects Many People
          Priority: Normal
         Component: bin
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: lyndon@orthanc.ca

Generic kernels have no ALTQ support.  pfctl barks:

  No ALTQ support in kernel
  ALTQ related functions disabled

every time it is run when the kernel doesn't have ALTQ support.

This is useless noise. The default kernels are not compiled with ALTQ, and the
majority of pf users don't use queues anyway.  pfctl already fails with an
appropriate diagnostic when faced with an altq-related directive in the absence
of ALTQ support, so why not move this diagnostic into that specific error
scenario?

The current behavior just annoys: (a) those who don't care, (b) those who don't
know about ALTQ, and (c) those who have to explain to (b) that their firewall
has not suddenly been breached by hordes of hackers.

Can we please move this diagnostic out of the default code path and into a more
appropriate location?

-- 
You are receiving this mail because:
You are the assignee for the bug.