Hello,
Am 28.03.2011 um 16:25 schrieb Florian Hinzmann:
Do you have (another) dig binary within your search path
or within
"/usr/ucb:/usr/bsd:/bin:/usr/bin:/usr/local/bin:/usr/share/bin:/usr/
com/bin",
what is what dlint searches.
Nope, nothing
~ $ which dig
/usr/bin/dig
What does "type dig" resp. "which dig" and "dig -v" say?
~ $ type dig
dig is hashed (/usr/bin/dig)
~ $ dig -v
DiG 9.7.2-P3
Please allow another question before I return to this issue
later: Which shell do you use when this problem occurs?
Bash.
Since dlint is a shell script, I will add debugging output here:
~ $ bash -x dlint pocnet.net
+ test x/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games:/home/poc/
bin:/usr/sbin:/sbin:/usr/local/sbin = x
+ PATH=/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games:/home/poc/
bin:/usr/sbin:/sbin:/usr/local/sbin:/usr/ucb:/usr/bsd:/bin:/usr/bin:/
usr/local/bin:/usr/share/bin:/usr/com/bin
+ export PATH
+ VERSION=1.4.0
+ rrfilt=/usr/share/dlint/digparse
++ tempfile --prefix=dlintns
+ TMPNS=/tmp/dlintkufa3x
++ tempfile --prefix=dlintzone
+ TMPZONE=/tmp/dlintKRgazA
++ tempfile --prefix=dlintptr
+ TMPPTR=/tmp/dlintsdRDWA
++ tempfile --prefix=dlinta
+ TMPA=/tmp/dlintWfpAfB
++ tempfile --prefix=dlintsubdoms
+ TMPSUBDOMS=/tmp/dlint9q8AyB
++ tempfile --prefix=dlinterr
+ TMPERR=/tmp/dlintRRvEmz
++ tempfile --prefix=dlinterr2
+ TMPERR2=/tmp/dlintgSWnEz
++ tempfile --prefix=dlintserials
+ TMPSERIALS=/tmp/dlintF7akXz
+ trap 'rm -f /tmp/dlintkufa3x /tmp/dlintKRgazA /tmp/dlintsdRDWA /tmp/
dlintWfpAfB /tmp/dlint9q8AyB /tmp/dlintRRvEmz /tmp/dlintgSWnEz; exit
4' 1 2 3 15
+ test 1 -lt 1 -o 1 -gt 2
++ echo -n hello
++ wc -l
+ test 0 -eq 0
+ echoc=
+ echon=-n
++ dig localhost any
++ head -1
++ grep DiG
++ sed -e 's/.*DiG \([0-9.]*\).*/\1/'
+ ver=
++ echo
++ awk '$1 >= 2.1 {print "ok"; exit}'
+ ans=
+ test x '!=' xok
+ echo ';; This program requires DiG version 2.1 or newer, which I
cannot find.'
;; This program requires DiG version 2.1 or newer, which I cannot find.
+ exit 3
After a bit of searching, I tried dlint with another user and that
works out ok.
Reason is that my user has a .digrc which makes dig more terse by
suppressing information I usually don't want to see.
Contents:
+ret=2 +noauthority +noadditional +noquestion +nostats +nocmd
Now I'm no longer sure if dig stopped working with the squeeze-upgrade
or way earlier when adding a .digrc.
How to cope with that properly?
Thanks for taking time and sorry for not debugging in the first place
myself.
:wq! PoC
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
