Re: problem with cron and wgreindex

[Golda Velez <gvelez@iwhome.com>]

You're right, there is no place where "whereis" should be used, as its not
generally available on all Unix platforms.  The makenh script does use the find
command, but not whereis.  Is it possible find or another command is aliased to
whereis?

If you just want to avoid the error message, you can modify the line to

 /home/2/c/coolrun/virtual_html/results/00/wgreindex -q 1> /dev/null 2>
/dev/null &

so that both stdout and stderr are redirected to a bitbucket.  (This works in
bourne shell, I'm not positive about ksh)

--G


On Thu, 03 Aug 2000, Tom Amiro wrote:
> I can't figure out why cron is sending me the following email from
> the cron job I setup to do glimpse reindexing.
> 
> > Your "cron" job on coolrunning
> > /home/2/c/coolrun/virtual_html/results/00/wgreindex -q > /dev/null
> >
> > produced the following output:
> >
> > ksh: whereis:  not found
> 
> I can't find any attempt to use the 'whereis' command
> in any of the scripts involved in re-indexing. And I
> thought the > /dev/null would have prevented
> the email anyway (assuming the problem was innocuos).
> 
> Tom
-- 
------------------------------------------------------------
Golda Velez         gvelez@iwhome.com	        520-620-6878
Internet Workshop                          http://iwhome.com
Webglimpse Search Software             http://webglimpse.net
		~~~~~~~~~~~~~~~~~~~~~~~~~~~
 Help organize the world - index your own corner of the web