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
"Include your script(s) in the respective /usr/local/outset/login-once/ or /usr/local/outset/login-every/ directory, and place a script in /usr/local/outset/on-demand/ that calls one or both of the above commands, it will loop through and process the scripts in the expected context."
The login-once items are processed successfully. However, the processing does not log this run to the preference file as is stated below: -
"This means, if your script was added to /usr/local/outset/login-once/ and you run the --login-once argument in your on demand script, then Outset will treat it like any other login-once item by processing it and logging it in the preference file so that subsequent logins won't run this script again."
This means that the new login-once script gets processed again at the next login so it ends up running again.
Running through the above scenario should add a run_once key for the script the was successfully triggered by the on-demand action.
The text was updated successfully, but these errors were encountered:
As per https://github.com/macadmins/outset/wiki/OnDemand, if I create a script in the on-demand folder that fires a --login-once trigger as per below: -
"Include your script(s) in the respective /usr/local/outset/login-once/ or /usr/local/outset/login-every/ directory, and place a script in /usr/local/outset/on-demand/ that calls one or both of the above commands, it will loop through and process the scripts in the expected context."
The login-once items are processed successfully. However, the processing does not log this run to the preference file as is stated below: -
"This means, if your script was added to /usr/local/outset/login-once/ and you run the --login-once argument in your on demand script, then Outset will treat it like any other login-once item by processing it and logging it in the preference file so that subsequent logins won't run this script again."
This means that the new login-once script gets processed again at the next login so it ends up running again.
Running through the above scenario should add a run_once key for the script the was successfully triggered by the on-demand action.
The text was updated successfully, but these errors were encountered: