Better error codes for glidein_startup.sh
A ticket was opened recently against Purdue for possible black hole node behavior. No logs are being returned to the factory so the operators cannot do much to help the site. Purdue admins found some nodes where glidein_startup.sh was failing with an error code of 1 and wanted to see the script to determine what was failing. The problem is that any failure returns error code 1. It is impossible to determine what went wrong without catching a failure in the act.
A proposed solution would be to have different error codes for different failure modes. For example, if invalid arguments are passed to the script give an error code of 1, if the validation scripts fail, give an error code of 2, etc.