If I'm going to run a scheduled task that executes bash and runs a shell script, do I need to specify full path to all of the commands that are going to be run?
I've run into some issues with my scripts where it seems as if they run well if I'm in bash when I run them, but if I schedule them or attempt to run them from the console (ex. bash sys:\var\script\script.sh), they churn out a bunch of command not found lines, then quit.

in testing I had noticed if I locate the nlm (ex. /usr/bin/wget) and use the full path to it, it will work. I would think there is an easier way though, am I able to just export the path at the beginning of my script? I've seen some other peoples examples of shell scripts in netware, but don't see anyone using full path or having to set the path in their examples.