Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 31 Aug 2020 10:37:42 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 249027] net-mgmt/monitoring-plugins unable to set port with check_dig
Message-ID:  <bug-249027-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D249027

            Bug ID: 249027
           Summary: net-mgmt/monitoring-plugins unable to set port with
                    check_dig
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: mat@FreeBSD.org
          Reporter: joakim.lindblom@loopia.se
             Flags: maintainer-feedback?(mat@FreeBSD.org)
          Assignee: mat@FreeBSD.org

Using -p for check_dig seems to put the port option for drill after name and
server arguments which does not seem to work when using drill.

check_dig -v -H 10.10.10.10 -p 5353 -l test.test
will run
/usr/bin/drill  @10.10.10.10 -z -p 5353  test.test A

An ugly hack with a manual argument seems to work as the port argument will=
 be
placed earlier in the command.

check_dig -v -H 10.10.10.10 -p 5353 -l test.test -A '-p 5353'
will run
/usr/bin/drill -p 5353 @10.10.10.10 -z -p 5353  test.test A

The first drill command will ignore the port option but the second will wor=
k.

The man pages for drill says "drill [ OPTIONS ] name [ @server ] [ type ] [
class ]" so this argument might need to be moved to a former position in the
command.

Maybe this should be solved in the extra-patch-dig-to-drill.diff file?

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-249027-7788>