When testing outset I get a bad permissions error. Anyone come across this? I have them set to 755, thanks!
Bad permissions: /usr/local/outset/login-once/dockutilscript.sh
The script shouldn't care as long as it has read and execute, but the LaunchDaemons / LaunchAgents have to be exact otherwise you'll get that error. Does Outset use a LaunchAgent to do its thing?
I'm not really sure about that, sorry I'm new to all of this. After imaging the machine I can login and see that the dock hasn't changed (the dock is what I'm changing with outset). I click the outset executable file and get this error:
outset: error: one of the arguments --boot --login, etc is required.
I'm sure it's something really simple that I'm overlooking. Thanks.
What is the file you're clicking?
I click the outset executable file and get this error
Outset would normally just run anything in the login-once folder so the error is sounding like it's not related.
Thats the one. I f you run it manually, it expects extra options to tell it what to do (like
--login or similar).
In this case, I would normally add some kind of logging to the script so you can at least tell if it is running or not. If you add a few lines like this:
echo "script has run" >> /Library/Logs/dockscript.log
You will get a log file in that location that will let you know if it's being triggered.
Outset is only able to run the script, so if it is running ok but not having the desired effect, it may be something in the script.
Yeah it works fine if I run it manually.
Posting a screenshot too.
/usr/local/bin/dockutil --remove all --no-restart
/usr/local/bin/dockutil --add /Applications/Launchpad.app /usr/local/bin/dockutil --add /Applications/Safari.app /usr/local/bin/dockutil --add /Applications/Firefox.app /usr/local/bin/dockutil --add /Applications/Google Chrome.app /usr/local/bin/dockutil --add /Applications/Notes.app /usr/local/bin/dockutil --add /Applications/Calendar.app /usr/local/bin/dockutil --add /Applications/Microsoft Word.app /usr/local/bin/dockutil --add /Applications/Microsoft Excel.app /usr/local/bin/dockutil --add /Applications/Microsoft PowerPoint.app /usr/local/bin/dockutil --add /Applications/Managed Software Center.app /usr/local/bin/dockutil --add /Applications/System Preferences.app /usr/local/bin/dockutil --add '~/Downloads' --view list
That all looks correct. Scripts in the login-once folder run in the user context so that shouldn't be affecting it. I compared your script to the example here: https://github.com/chilcote/outset/wiki/Dockutil
All looks the same (or similar)
The error about writing to the log file is normal if you run it manually. That being said, if you're running a login-once script, the user probably doesn't have the permissions to write to it either. Try setting the log file location to somewhere the user can write to (possibly /Users/Shared) and try again. Outset may be running the script after all.
Yep that works. I can run the script manually and the log file outputs to the /Users/Shared folder, but I'm still getting
Bad permissions: /usr/local/outset/login-once/dockutilscript.sh when doing /usr/local/outset/outset --login
So, we've verified that the script is working. What else could it be?
I read that yesterday. He says that it's been fixed, but it's still not working for me.
/usr/local/outset/outset --login-once returns the bad permissions error
sudo /usr/local/outset/outset --login-once works