You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
in some case the jamfhelper killed by terminal or Activity Monitor it will not return 239 error code and return empty intend
old code
checkAttemptToQuit(){
Value="${1}"
# Jamf Helper was exited without making a choice
if [[ "$Value" == "239" ]]; then
echo "Jamf Helper was exited without making a choice."
"$jamf" policy -event "$CustomTriggerNameDeprecationPolicy" &
exit 0
fi
}
fix
checkAttemptToQuit(){
Value="${1}"
# Jamf Helper was exited without making a choice
# pngo 12/31/21: include empty return code
# The 239 return value is defaults when user quit the jamfhelper (Command+Q) if user kill it using kill [pid] command it will return empty
if [[ "$Value" == "239" ]] || [[ -z "$Value" ]]; then
echo "Jamf Helper was exited without making a choice."
"$jamf" policy -event "$CustomTriggerNameDeprecationPolicy" &
exit 0
fi
}
The text was updated successfully, but these errors were encountered:
phu-ngo
changed the title
checkAttemptToQuit() function will not quit if input value is empty
OSUpdateNotifier: checkAttemptToQuit() function will not quit if input value is empty
Jan 10, 2022
in some case the jamfhelper killed by terminal or Activity Monitor it will not return 239 error code and return empty intend
old code
fix
The text was updated successfully, but these errors were encountered: