Hello

What do I need to do to make the system script of a scheduled script sequence FAIL?

In the documentation it says that the system script needs to return "0" for the FileMaker Script portion to start. I observed this to be true with Server 10.0v1 on OS X Server 10.5.X

Now I am running Server 10.0v2 on OS X server 10.6.2 and even a .sh file with nothing in it except #!/bin/sh will run, evaluate to true and let the fileMaker script run.

Has anyone encountered this with server 10.0v2?

Currently my bash script ends with:

if [ $Sucess -gt 0 ]; then

echo 0

else

echo "DO NOT RUN!"

fi

Both cases will allow the FileMaker portion of the script sequence to run. (I also tried # echo "DO NOT RUN!" >&2 and that didn't work either.

Thanks!

Edited December 2, 200916 yr by Guest
fixed version numbers

ok, I'm a moron and was looking at a debug version of the script that used echo instead of exit.

exit 0 will allow the fileMaker Script to proceed, but exit [anything else] will cause it to fail. (using bash at least.)

so by default an empty script will exit 0 and that's why it was allowing the fileMaker script to proceed after running an empty bash script.

Crisis Averted!