Jeff Kinz wrote: > Realistically, the absolute path to a command technique will never enter > general use. > > I do use it myself when building installation tools or when developing > tools which will run as third party software on other peoples systems. > Like the "configure" tool - you should never assume much about how any > other site is configured. Fortunately, like "configure" it easy to do a > little bit of probing and set these values up to be used as needed > in a variable. Then they can be used easily without fear and without > awkwardness. For example "LS=/bin/ls" (after to checking to see if it is > in deed there) then for "ls" simply use $LS as needed. This is a common > approach seen in many scripts. Maybe, but why not simply reset PATH to something you know is good? (I'm snipping a lot of good stuff...) James. -- E-mail address: james | Mike Andrews' Corollary to Murphy's Law: @westexe.demon.co.uk | In any sufficiently large collection of texts, every | possible misspeeling, as well as some that are not | possible, will occur.