I have a policy that is running a shell script using "#!/bin/sh -v", which prints the contents of the script to the log for debug/testing purposes. Regardless of whether or not the -v option is there, the logs show that the script returns an exit code of 0, but the policy fails after running the script when -v option is present. Is anyone aware of a bug that could be related to this?
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.