At 11:02 PM 2/6/00 -0500, you wrote:
>(just found out the hard way) the path to xloadimage:
>
>31 * * * * /usr/X11R6/bin/xloadimage -onroot etc
$ which xloadimage
/usr/X11R6/bin/xloadimage
$
Interesting what you find when you poke randomly in man pages and other
docs. Or read a random shell script from the system and man everything
unfamiliar you see in the file that looks like it might be a command or a
standard file name.
The "which" thing, to find out what exact directory a command on your path
is in, is a nice example of a very useful and simple utility totally
lacking in MS-DOS. Especially useful when debugging problems that can be
caused by having conflicting versions of stuff on the path, i.e. app a
needs a newer version of utility b, and an older version of utility b is
also on the path -- which will indicate this problem exists and probably
even show that the old one is earlier on the path, not to mention indicate
where it is lurking so you can rm it or at least mv it off the path.
--
.*. "Clouds are not spheres, mountains are not cones, coastlines are not
-() < circles, and bark is not smooth, nor does lightning travel in a
`*' straight line." -------------------------------------------------
-- B. Mandelbrot |http://surf.to/pgd.net [EMAIL PROTECTED]
_____________________ ____|________ Paul Derbyshire
Programmer & Humanist|ICQ: 10423848|
