Path: utzoo!attcan!uunet!snorkelwacker!paperboy!meissner From: meissner@osf.org (Michael Meissner) Newsgroups: comp.unix.questions Subject: Re: Which script (was Re: comp.unix.questions) Message-ID: Date: 22 Sep 90 18:21:34 GMT References: <574@DIALix.UUCP> <13992@hydra.gatech.EDU> Sender: root@OSF.ORG Organization: Open Software Foundation Lines: 22 In-reply-to: gt0178a@prism.gatech.EDU's message of 22 Sep 90 10:19:37 GMT In article <13992@hydra.gatech.EDU> gt0178a@prism.gatech.EDU (BURNS,JIM) writes: | > The purpose of the which tool is to tell you _which_ command will be | > executed. It is designed to be quick. It does not attempt to | > interpret functions, aliases or similar creatures. | | I'm using it to find out where an executable lives. Useful if your system | has several versions, and which you execute depends on how your PATH is | ordered. And since I *can't* execute wall(1) (or finger(1)) on that | machine, locating it tells me why - it's not that it's not there, just | that it's not world executable. By extension, I have an $ETC variable I | can also search for the occaisional command that's not normally in my | $PATH, like ping(1). I like bash's type -all feature, where you can find all occurances of a command in the PATH. -- Michael Meissner email: meissner@osf.org phone: 617-621-8861 Open Software Foundation, 11 Cambridge Center, Cambridge, MA, 02142 Do apple growers tell their kids money doesn't grow on bushes?