On 7/20/07, Bhasker C V <[EMAIL PROTECTED]> wrote:
Bash sometimes caches the filenames along with path names
and i have faced this some times
Closing the bash shell and opening another shell must fix the problem
good catch, that was it! (all other shells could run 'lsof' fine, just
the one had trouble). thanks!
unless there is a stray /usr/sbin/lsof present which is wrongly pointing
to some file.
also I have always thought it is a good idea to put /usr/bin first in
the path and /usr/sbin , /sbin must be prepended only for root shells.
sudo lsof must also work.
indeed it does.
On Fri, 2007-07-20 at 10:16 -0500, will trillich wrote:
> # apt-get install lsof
> Reading package lists... Done
> Building dependency tree... Done
> The following NEW packages will be installed
> lsof
> 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> Need to get 0B/205kB of archives.
> After unpacking 369kB of additional disk space will be used.
> Selecting previously deselected package lsof.
> (Reading database ... 49097 files and directories currently installed.)
> Unpacking lsof (from .../lsof_4.77.dfsg.1-3_i386.deb) ...
> Setting up lsof (4.77.dfsg.1-3) ...
>
> # lsof -i
> bash: /usr/sbin/lsof: No such file or directory
>
> say what?
>
> # ls -l `which lsof`
> -rwxr-xr-x 1 root root 106324 2006-05-15 18:09 /usr/bin/lsof*
>
> eh? any ideas?
>
> --
> will trillich
> "The only way to be truly satisfied is to do what you believe is great
> work -- and the only way to do great work is to love what you do."
> -- Steve Jobs
>
>
--
Bhasker C V
Registered Linux user: #306349 (counter.li.org)
The box said "Requires Windows 95, NT, or better", so I installed Linux.
--
will trillich
"The only way to be truly satisfied is to do what you believe is great
work -- and the only way to do great work is to love what you do."
-- Steve Jobs
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
