Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #205507 > unrolled thread

lost dig

Started bytony <lists@vanderhoff.org>
First post2019-02-19 12:20 +0100
Last post2019-02-19 17:10 +0100
Articles 11 — 6 participants

Back to article view | Back to linux.debian.user


Contents

  lost dig tony <lists@vanderhoff.org> - 2019-02-19 12:20 +0100
    Re: lost dig john doe <johndoe65534@mail.com> - 2019-02-19 12:30 +0100
      Re: lost dig Claudio Kuenzler <ck@claudiokuenzler.com> - 2019-02-19 13:00 +0100
        Re: lost dig tony <lists@vanderhoff.org> - 2019-02-19 13:10 +0100
          Re: lost dig <tomas@tuxteam.de> - 2019-02-19 13:20 +0100
      Re: lost dig tony <lists@vanderhoff.org> - 2019-02-19 13:00 +0100
        Re: lost dig Claudio Kuenzler <ck@claudiokuenzler.com> - 2019-02-19 13:10 +0100
    Re: lost dig Martin <keine-eile@online.de> - 2019-02-19 13:40 +0100
      Re: lost dig Martin <keine-eile@online.de> - 2019-02-19 13:50 +0100
        Re: lost dig <tomas@tuxteam.de> - 2019-02-19 14:00 +0100
    Re: lost dig Mike McClain <mike.junk.46@att.net> - 2019-02-19 17:10 +0100

#205507 — lost dig

Fromtony <lists@vanderhoff.org>
Date2019-02-19 12:20 +0100
Subjectlost dig
Message-ID<xtbBn-4im-5@gated-at.bofh.it>
In my fiddling with DNS, I installed (as su) a python package from pypi
called 'dig'. It turned out to not be what I expected, so I abandoned it.

However, now when I enter 'dig' on the command line, it runs this python
thing. So I uninstalled dig from python, using 'pip3 uninstall dig'.
That seemed to work fine, but now when I type 'dig' at the terminal, I
get bash: /usr/local/bin/dig: No such file or directory. Well, that's OK
because dig - the proper one - is at /usr/bin/dig.

'which dig' gives me '/usr/bin/dig/

So, how do I now get the alias (if that's what it is) to point at the
right file?

Thanks, Tony

[toc] | [next] | [standalone]


#205508

Fromjohn doe <johndoe65534@mail.com>
Date2019-02-19 12:30 +0100
Message-ID<xtbL3-4lj-1@gated-at.bofh.it>
In reply to#205507
On 2/19/2019 12:10 PM, tony wrote:
> In my fiddling with DNS, I installed (as su) a python package from pypi
> called 'dig'. It turned out to not be what I expected, so I abandoned it.
>
> However, now when I enter 'dig' on the command line, it runs this python
> thing. So I uninstalled dig from python, using 'pip3 uninstall dig'.
> That seemed to work fine, but now when I type 'dig' at the terminal, I
> get bash: /usr/local/bin/dig: No such file or directory. Well, that's OK
> because dig - the proper one - is at /usr/bin/dig.
>
> 'which dig' gives me '/usr/bin/dig/
>
> So, how do I now get the alias (if that's what it is) to point at the
> right file?
>

Isn't the alias defined in '~/.bashrc' or '~/.bash_aliases'?

--
John Doe

[toc] | [prev] | [next] | [standalone]


#205510

FromClaudio Kuenzler <ck@claudiokuenzler.com>
Date2019-02-19 13:00 +0100
Message-ID<xtce6-4uJ-13@gated-at.bofh.it>
In reply to#205508

[Multipart message — attachments visible in raw view] — view raw

On 2/19/2019 12:10 PM, tony wrote:
> > In my fiddling with DNS, I installed (as su) a python package from pypi
> > called 'dig'. It turned out to not be what I expected, so I abandoned it.
> >
> > However, now when I enter 'dig' on the command line, it runs this python
> > thing. So I uninstalled dig from python, using 'pip3 uninstall dig'.
> > That seemed to work fine, but now when I type 'dig' at the terminal, I
> > get bash: /usr/local/bin/dig: No such file or directory. Well, that's OK
> > because dig - the proper one - is at /usr/bin/dig.
> >
> > 'which dig' gives me '/usr/bin/dig/
> >
> > So, how do I now get the alias (if that's what it is) to point at the
> > right file?
>

First check with "alias" if there is really still some alias defined which
points to /usr/local/bin/dig.
You might also have to logout and login again to clear your environment.

[toc] | [prev] | [next] | [standalone]


#205512

Fromtony <lists@vanderhoff.org>
Date2019-02-19 13:10 +0100
Message-ID<xtcnL-4Nd-1@gated-at.bofh.it>
In reply to#205510
On 19/02/2019 12:53, Claudio Kuenzler wrote:
> 
> 
>     On 2/19/2019 12:10 PM, tony wrote:
>     > In my fiddling with DNS, I installed (as su) a python package from
>     pypi
>     > called 'dig'. It turned out to not be what I expected, so I
>     abandoned it.
>     >
>     > However, now when I enter 'dig' on the command line, it runs this
>     python
>     > thing. So I uninstalled dig from python, using 'pip3 uninstall dig'.
>     > That seemed to work fine, but now when I type 'dig' at the terminal, I
>     > get bash: /usr/local/bin/dig: No such file or directory. Well,
>     that's OK
>     > because dig - the proper one - is at /usr/bin/dig.
>     >
>     > 'which dig' gives me '/usr/bin/dig/
>     >
>     > So, how do I now get the alias (if that's what it is) to point at the
>     > right file?
> 
> 
> First check with "alias" if there is really still some alias defined
> which points to /usr/local/bin/dig.

No alias.

> You might also have to logout and login again to clear your environment.
> 
Woo, yes, of course. That works fine. Many thanks!

[toc] | [prev] | [next] | [standalone]


#205514

From<tomas@tuxteam.de>
Date2019-02-19 13:20 +0100
Message-ID<xtcxr-4Qd-3@gated-at.bofh.it>
In reply to#205512

[Multipart message — attachments visible in raw view] — view raw

On Tue, Feb 19, 2019 at 01:01:36PM +0100, tony wrote:
> On 19/02/2019 12:53, Claudio Kuenzler wrote:

[...]

> > First check with "alias" if there is really still some alias defined
> > which points to /usr/local/bin/dig.
> 
> No alias.
> 
> > You might also have to logout and login again to clear your environment.
> > 
> Woo, yes, of course. That works fine. Many thanks!

This was your shell's cached association (name -> full-path). If your shell
is bash, then 'hash' is the builtin to use when you want to inspect/modify
that cache.

For example, "hash -r" or "hash -d dig" might have been sufficient in the
above situation. Try hash -l to list all current entries.

Cheers
-- t

[toc] | [prev] | [next] | [standalone]


#205511

Fromtony <lists@vanderhoff.org>
Date2019-02-19 13:00 +0100
Message-ID<xtce6-4uJ-11@gated-at.bofh.it>
In reply to#205508
On 19/02/2019 12:22, john doe wrote:
> On 2/19/2019 12:10 PM, tony wrote:
>> In my fiddling with DNS, I installed (as su) a python package from pypi
>> called 'dig'. It turned out to not be what I expected, so I abandoned it.
>>
>> However, now when I enter 'dig' on the command line, it runs this python
>> thing. So I uninstalled dig from python, using 'pip3 uninstall dig'.
>> That seemed to work fine, but now when I type 'dig' at the terminal, I
>> get bash: /usr/local/bin/dig: No such file or directory. Well, that's OK
>> because dig - the proper one - is at /usr/bin/dig.
>>
>> 'which dig' gives me '/usr/bin/dig/
>>
>> So, how do I now get the alias (if that's what it is) to point at the
>> right file?
>>
> 
> Isn't the alias defined in '~/.bashrc' or '~/.bash_aliases'?
> 
no...

[toc] | [prev] | [next] | [standalone]


#205513

FromClaudio Kuenzler <ck@claudiokuenzler.com>
Date2019-02-19 13:10 +0100
Message-ID<xtcnM-4Nd-7@gated-at.bofh.it>
In reply to#205511

[Multipart message — attachments visible in raw view] — view raw

On Tue, Feb 19, 2019 at 12:55 PM tony <lists@vanderhoff.org> wrote:

>
> > Isn't the alias defined in '~/.bashrc' or '~/.bash_aliases'?
> >
> no...
>

Maybe it's not an alias at all but rather an "alternative". Check
"update-alternatives --get-selections" if there is an entry for dig.

[toc] | [prev] | [next] | [standalone]


#205515

FromMartin <keine-eile@online.de>
Date2019-02-19 13:40 +0100
Message-ID<xtcQN-4W0-7@gated-at.bofh.it>
In reply to#205507
The DNS lookup utility 'dig' is part of the package 'dnsutils'.

Am 19.02.19 um 12:10 schrieb tony:
> In my fiddling with DNS, I installed (as su) a python package from pypi
> called 'dig'. It turned out to not be what I expected, so I abandoned it.
> 
> However, now when I enter 'dig' on the command line, it runs this python
> thing. So I uninstalled dig from python, using 'pip3 uninstall dig'.
> That seemed to work fine, but now when I type 'dig' at the terminal, I
> get bash: /usr/local/bin/dig: No such file or directory. Well, that's OK
> because dig - the proper one - is at /usr/bin/dig.
> 
> 'which dig' gives me '/usr/bin/dig/
> 
> So, how do I now get the alias (if that's what it is) to point at the
> right file?
> 
> Thanks, Tony
> 

[toc] | [prev] | [next] | [standalone]


#205516

FromMartin <keine-eile@online.de>
Date2019-02-19 13:50 +0100
Message-ID<xtd0t-4Z4-3@gated-at.bofh.it>
In reply to#205515
Sorry, was a little quick on that.

Like said, the (ISC) DNS lookup utility 'dig' is part of the package 'dnsutils'.
I do not have an alias set or an alternatives record for this.
Do you have a '/etc/alternatives/dig'? If yes, deleting it should be fine, as long as  /usr/bin/dig exists 


Am 19.02.19 um 13:37 schrieb Martin:
> The DNS lookup utility 'dig' is part of the package 'dnsutils'.
> 
> Am 19.02.19 um 12:10 schrieb tony:
>> In my fiddling with DNS, I installed (as su) a python package from pypi
>> called 'dig'. It turned out to not be what I expected, so I abandoned it.
>>
>> However, now when I enter 'dig' on the command line, it runs this python
>> thing. So I uninstalled dig from python, using 'pip3 uninstall dig'.
>> That seemed to work fine, but now when I type 'dig' at the terminal, I
>> get bash: /usr/local/bin/dig: No such file or directory. Well, that's OK
>> because dig - the proper one - is at /usr/bin/dig.
>>
>> 'which dig' gives me '/usr/bin/dig/
>>
>> So, how do I now get the alias (if that's what it is) to point at the
>> right file?
>>
>> Thanks, Tony
>>
> 

[toc] | [prev] | [next] | [standalone]


#205517

From<tomas@tuxteam.de>
Date2019-02-19 14:00 +0100
Message-ID<xtda9-52d-3@gated-at.bofh.it>
In reply to#205516

[Multipart message — attachments visible in raw view] — view raw

On Tue, Feb 19, 2019 at 01:42:27PM +0100, Martin wrote:
> Sorry, was a little quick on that.
> 
> Like said, the (ISC) DNS lookup utility 'dig' is part of the package 'dnsutils'.
> I do not have an alias set or an alternatives record for this.
> Do you have a '/etc/alternatives/dig'? If yes, deleting it should be fine, as long as  /usr/bin/dig exists 

The problem seems to be solved. It seems to have been
the shell cache remembering the old association. Nothing
permanent. Reread thread.

Cheers
-- t

[toc] | [prev] | [next] | [standalone]


#205522

FromMike McClain <mike.junk.46@att.net>
Date2019-02-19 17:10 +0100
Message-ID<xtg82-6Yk-11@gated-at.bofh.it>
In reply to#205507
On Tue, Feb 19, 2019 at 12:10:15PM +0100, tony wrote:
> In my fiddling with DNS, I installed (as su) a python package from pypi
> called 'dig'. It turned out to not be what I expected, so I abandoned it.
>
> However, now when I enter 'dig' on the command line, it runs this python
> thing. So I uninstalled dig from python, using 'pip3 uninstall dig'.
> That seemed to work fine, but now when I type 'dig' at the terminal, I
> get bash: /usr/local/bin/dig: No such file or directory. Well, that's OK
> because dig - the proper one - is at /usr/bin/dig.
>
> 'which dig' gives me '/usr/bin/dig/
>
> So, how do I now get the alias (if that's what it is) to point at the
> right file?
>
> Thanks, Tony

Try hash -d dig.

Bash keeps a list of where executed commands are so it doesn't have to
look them every time.

Cheers,
Mike
--
Be Here now, just breathe.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.user


csiph-web