Bug 193442 – sometime "which" just fails to find a file

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 193442 - sometime "which" just fails to find a file

Summary:	sometime "which" just fails to find a file

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	which (Show other bugs)
Sub Component:
Version:	4
Hardware:	i586 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Ngo Than
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:	Reopened

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2006-05-28 14:52 EDT by james
Modified:	2007-11-30 17:11 EST (History)
CC List:	0 users

See Also:
Fixed In Version:	F8
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2007-09-13 10:36:24 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description james 2006-05-28 14:52:48 EDT

Description of problem:
$ ll /usr/sbin/privoxy
-rwxr--r--  1 privoxy privoxy 190480 Mar  2  2005 /usr/sbin/privoxy*

$ which /usr/sbin/privoxy
which: no privoxy in (/usr/sbin)


Version-Release number of selected component (if applicable):
$ rpm -qf /usr/bin/which
which-2.16-6


How reproducible:
with that file, always.

Comment 1 Ngo Than 2006-10-10 13:38:30 EDT

The problem is that /usr/sbin is not in PATH. which only looks the programname
in the PATH.

You have to add PATH=/usr/sbin:$PATH.

Comment 2 james 2006-10-10 13:58:37 EDT

Ha, ha, ha!  No, /usr/sbin _is_ in my $PATH, and so this is a bit odd.

I'm now using which-2.16-6.2.1, and which still couldn't find "privoxy" on a bet.

So, unless there is some hardcoded PATH in "which", the "NotABug" label is
wishful thinking.  Look a little deeper...

Comment 3 Christian Iseli 2007-01-19 19:21:31 EST

This report targets the FC3 or FC4 products, which have now been EOL'd.

Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?

Thanks.

Comment 4 Ngo Than 2007-09-13 10:36:24 EDT

it's not reproduceable in F8.

Note You need to log in before you can comment on or make changes to this bug.