ports/130069: PATCH: flow-rptfmt in net-mgmt/flow-tools-ng does not work

Michael W Lucas mwlucas at blackhelicopters.org
Tue Dec 30 23:50:06 UTC 2008


>Number:         130069
>Category:       ports
>Synopsis:       PATCH:  flow-rptfmt in net-mgmt/flow-tools-ng does not work
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Dec 30 23:50:00 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Michael W Lucas
>Release:        8.0-CURRENT
>Organization:
none
>Environment:
FreeBSD stretchlimo.blackhelicopters.org 8.0-CURRENT FreeBSD 8.0-CURRENT #16: Tue Dec 16 10:22:25 EST 2008     mwlucas at stretchlimo.blackhelicopters.org:/usr/obj/usr/src/sys/GENERIC  i386

>Description:
Checked on a recent -current with 16 Dec 2008 ports tree.  No update
for net-mgmt/flow-tools-ng on cvsweb.

The flow-rptfmt utility has the path to env hard-coded to /bin/env.
FreeBSD has /usr/bin/env instead.  flow-rptfmt is the recommended way to
create reports from flow-tools data (even though clearly nobody uses
it except me. :-)

This is probably applicable for net-mgmt/flow-tools/ as well.

FreeBSD is the reference platform for my network analysis book, so I'd really like to see this fixed.
>How-To-Repeat:
Install flow-tools-ng.  Get some data.  Try to use flow-report with a
default stat.cfg, i.e.:

# flow-cat ft-v05.2008-12-01.12* | flow-report -v TYPE=ip-source/destination-port -v SORT=+flows | less

Watch it fail.


>Fix:
See the attached (trivial) patch.

Patch attached with submission follows:

--- bin/flow-rptfmt.orig	2008-12-30 18:25:58.000000000 -0500
+++ bin/flow-rptfmt	2008-12-30 18:26:07.000000000 -0500
@@ -1,4 +1,4 @@
-#!/bin/env python
+#!/usr/bin/env python
 
 import sys
 import string


>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the freebsd-ports-bugs mailing list