Re: lost dig
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.
Re: lost dig
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 signature.asc Description: Digital signature
Re: lost dig
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 >> >
Re: lost dig
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 >
Re: lost dig
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 signature.asc Description: Digital signature
Re: lost dig
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!
Re: lost dig
On Tue, Feb 19, 2019 at 12:55 PM tony 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.
Re: lost dig
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...
Re: lost dig
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.
Re: lost dig
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
lost dig
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
