Re: Re: [pimppa-users] Bugs and wish list

[I. W. <iwr...@us...>]

On Tue, 11 Dec 2001, boz boz wrote:

> Then I realized that in crontab, at least in my crontab, the full path
> to an executable must be used in a command or else it won't find it.
> Crontab is a limited environment and doesn't know what the paths to
> executables are unless you tell it.

In the beginning of the crontab, just add

PATH=/bin:/usr/bin:/usr/local/bin:/usr/whatever:/blah/blah
                   ^^^^^^^^^^^^^^
etc ... ;) There's probably some path defined already. Just
add the usr/local/bin to it... Though it could be that
the path is not exported to the programs ran from crontab
in your system. Dunno.

> Since ptest couldn't read anything from the tmpfile it assumed the
> file tested bad and marked it as such.

No. That's not it. The tmpfile is not used at all if no
'ok string' is defined - then just the return value of
the command is used (some test programs do not follow
this return value mechanism, and we have to read result from 
the tmpfile). But in this case a return value '0' from 
jpeginfo means that the file was correct, and if the command
was not found, like in this case, shell returns something
nonzero, which usually in the unix world means an error,
and ptest thinks similarly. It could be adjusted to
check for 'command not found' too but I haven't done
that... 


Ok. End of lecture. ;)