net/flow-tools duplicate parts of path

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

net/flow-tools duplicate parts of path

marfabastewart
Synopsis:  duplicate parts of path for config files, flow-rptfmt
Category:  net/flow-tools
Environment:
  OpenBSD 6.7-current (GENERIC) #298: Sun Jun 28 13:05:49 MDT 2020
    [hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC
  Architecture: OpenBSD.amd64
  Machine   : amd64
Description:
  1. /usr/local/bin/flow-rptfmt starts with
  !/usr/usr/local/bin/python2.7 (two "/usr"s instead of one)

  2. There are also duplicate paths when calling flow-nfilter and maybe
  other programs. "/etc/flow-tools/flow-tools" instead of
  "/etc/flow-tools"

  3. (question) -- is splintered.net still up? I couldn't
  access it and email to get on the flow-tools mailing list at that
  domain also bounced). It's in flow-tools-0.68.6/README

How-To-Repeat:
  1. flow-cat ft-v05.2020-06-27.201501-0500 |flow-report

  2. $flow-cat ft-v05.2020-06-27.201501-0500 |flow-nfilter
  flow-nfilter: open(/etc/flow-tools/flow-tools/ip-prot.sym):
    No such file or directory
  flow-nfilter: open(/etc/flow-tools/flow-tools/tcp-port.sym):
    No such file or directory
  flow-nfilter: open(/etc/flow-tools/flow-tools/asn.sym):
    No such file or directory
  flow-nfilter: open(/etc/flow-tools/flow-tools/tag.sym):
    No such file or directory
  flow-nfilter: open(/etc/flow-tools/flow-tools/filter.cfg):
    No such file or directory
  flow-nfilter: ftfil_load(): failed

Fix:
  1. work around: removing the extra /usr in flow-rptfmt shebang
  2. work around: create extra flow-tools dir under /etc/flow-tools.

  Maybe the github changes to lib/ftpathc.s on Mar 21, 2019 and to
  flow-rptfmt on Mar 20, 2019 have something to do with this.

  My 6.7 stable box doesn't have these problems. I first installed
  the package while running 6.5 stable or 6.6 stable though.

  Please let me know if I can help with testing.



Sent with ProtonMail Secure Email.


Reply | Threaded
Open this post in threaded view
|

Re: net/flow-tools duplicate parts of path

Stuart Henderson
On 2020/06/29 03:10, marfabastewart wrote:

> Synopsis:  duplicate parts of path for config files, flow-rptfmt
> Category:  net/flow-tools
> Environment:
>   OpenBSD 6.7-current (GENERIC) #298: Sun Jun 28 13:05:49 MDT 2020
>     [hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC
>   Architecture: OpenBSD.amd64
>   Machine   : amd64
> Description:
>   1. /usr/local/bin/flow-rptfmt starts with
>   !/usr/usr/local/bin/python2.7 (two "/usr"s instead of one)
>
>   2. There are also duplicate paths when calling flow-nfilter and maybe
>   other programs. "/etc/flow-tools/flow-tools" instead of
>   "/etc/flow-tools"

Thanks, I've just fixed /etc/flow-tools/flow-tools and
/usr/usr/local/bin/python2.7 in -current. Please let me know if there
are other problems.

>   3. (question) -- is splintered.net still up? I couldn't
>   access it and email to get on the flow-tools mailing list at that
>   domain also bounced). It's in flow-tools-0.68.6/README

No idea.

> How-To-Repeat:
>   1. flow-cat ft-v05.2020-06-27.201501-0500 |flow-report
>
>   2. $flow-cat ft-v05.2020-06-27.201501-0500 |flow-nfilter
>   flow-nfilter: open(/etc/flow-tools/flow-tools/ip-prot.sym):
>     No such file or directory
>   flow-nfilter: open(/etc/flow-tools/flow-tools/tcp-port.sym):
>     No such file or directory
>   flow-nfilter: open(/etc/flow-tools/flow-tools/asn.sym):
>     No such file or directory
>   flow-nfilter: open(/etc/flow-tools/flow-tools/tag.sym):
>     No such file or directory
>   flow-nfilter: open(/etc/flow-tools/flow-tools/filter.cfg):
>     No such file or directory
>   flow-nfilter: ftfil_load(): failed
>
> Fix:
>   1. work around: removing the extra /usr in flow-rptfmt shebang
>   2. work around: create extra flow-tools dir under /etc/flow-tools.
>
>   Maybe the github changes to lib/ftpathc.s on Mar 21, 2019 and to
>   flow-rptfmt on Mar 20, 2019 have something to do with this.
>
>   My 6.7 stable box doesn't have these problems. I first installed
>   the package while running 6.5 stable or 6.6 stable though.
>
>   Please let me know if I can help with testing.
>
>
>
> Sent with ProtonMail Secure Email.
>
>