but I've noticed that some don't work as well

Sometimes converting from #!/bin/bash to #!/bin/sh work better, and with others just the reverse

Thoughts from any other engineers out there?

My first thought is that I need context and examples so I can give you some feedback.

trying to tie-up some of the loose ends with scripting

Again, it would be great if there was an example so I knew where to start. Thank you.

Thanks, Zan.

I can use the following script as an example, when trying to enable the function of selecting hot corners under 10.9 in bash. I haven't tested this if I changed #!/bin/bash to #!/bin/sh:

#!/bin/bash

# This script enables the bottom-left hot corner and starts the screen saver
defaults write com.apple.dock wvous-bl-corner -int 5

echo "script complete"

exit 0

The second example is a combo script that's not working either:

#!/bin/sh

# This script enables scroll bars always
sudo defaults write NSGlobalDomain AppleShowScrollBars -string “Always”

# This script enables status bar at the bottom of any finder window
sudo defaults write com.apple.finder ShowStatusBar -bool true

echo "script complete"

exit 0

sorry maybe i missed it but can you please post, and use the script tags on this forum to preserve the script formatting, a script that works in one shell but not the other?

It is likely that its a syntax issue. Generally all sh scripts will run under bash. but not all bash scripts will run under sh.

Also whats an XML script?

@ msample - Sir, thank you much. I was just about to start looking for the command to do this and just happened to look at this thread see the exact command I was looking for. Thank you for the commands!!

@ WUSLS - You're welcome, Scott. Test each of the scripts and let me know how they work for you. I'm simply testing both of these shells (i.e, bash or sh) to see how well they work, or if I need to re-write them in XML or python. I appreciate you comments.

All my bash scripts have #!/bin/sh

Never had to change it, & this is over 7 years of using the suite.

@ bentoms - Thanks, Ben.

One point: never use sudo inside of a script. Sudo should be used to execute the script if it needs root-level access. Casper will handle that for you when it executes scripts.

Keep in mind, that the binaries for both /bin/bash and /bin/sh are actually the same version of bash. So it really doesn't matter what you use.

1~ > /bin/sh --version
2GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin14)
3Copyright (C) 2007 Free Software Foundation, Inc.
4~ > /bin/bash --version
5GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin14)
6Copyright (C) 2007 Free Software Foundation, Inc.

@ alexjdale - Thanks Alex, my apologies, just a slip of the fingers while scripting. You're correct, sudo should always be dropped.

@msample

I believe your scripts may not be working because you have typed "curly" quotation marks in your example post up top. They look like the type of quotes that a word processor uses (also known as "typographer's quotes"). My guess is you're trying to write your BASH scripts in Text Edit or Microsoft Word. I recommend using Text Wrangler or XCode for editing scripts.

Also, I went ahead and took the liberty to write a script for you. It may solve your problem. I wrote this script as a reference because I wanted to programmatically get the user's home folder so I could use "defaults" to write to the full path to the preference file. The "defaults" program can be finicky when writing preferences to memory and to preference files.

I also added a function to write the user preference to any local user account plus the currently logged in user (sans root). This is under the assumption that the script is being launched with "sudo" (as Casper does). If you don't want to set preferences for all users, simply comment out (or delete) the 2nd-to-last line.

Please review and test this script before attempting to run it on a production machine. Thanks.

1#!/bin/bash
2# Author: Zan Bassi
3# Email: zan@zeroonelabs.com
4#
5# Terms of service: Use at your own risk.
6#
7# Gets the username of the user currently logged in. 
8# Will return "root" if no one is logged in through the Finder.
9currentuser="$(ls -l /dev/console | awk '{ print $3 }')"
10# Gets the full path of the user home folder. 
11# Will return "/var/root" if no user is logged in through the Finder.
12curuserhome="$(dscl . read /Users/"${currentuser}" NFSHomeDirectory | awk -F": " '{print $NF}')"
13
14# If there is a user logged in (who is not root), set it for that person.
15if [[ ! ${currentuser} = "root" ]];then
16  echo "Setting bottom-left hot corner for ${currentuser}."
17  defaults write "${curuserhome}"/Library/Preferences/com.apple.dock.plist wvous-bl-corner -int 5
18  echo "Setting status bar Finder preference for ${currentuser}."
19  defaults write "${curuserhome}"/Library/Preferences/com.apple.finder ShowStatusBar -bool true
20fi
21defaults write NSGlobalDomain AppleShowScrollBars -string "Always"
22
23_setPrefForAll () {
24    # Will return an array of full paths for any local user accounts on the machine.
25    # Each array index is separated by a newline character.
26    uhomearray=($(dscl . list /Users NFSHomeDirectory | grep -vE "/var|_www|^com" | awk '{print $NF}'))
27    # For each index in the array, do:
28    for UHOME in ${uhomearray[@]};do
29        # defaults write /Users/xxx/Library/...
30        echo "Setting bottom-left hot corner for the following user path: ${UHOME}."
31        defaults write "${UHOME}"/Library/Preferences/com.apple.dock.plist wvous-bl-corner -int 5
32        echo "Setting status bar Finder preference for the following user path: ${UHOME}."
33        defaults write "${UHOME}"/Library/Preferences/com.apple.finder ShowStatusBar -bool true
34    done
35}
36_setPrefForAll
37exit

Thanks, Zan. I'm testing this out today under 10.9.5 & 10.10.2. You were also correct concerning the quotes, not sure how that happened...but I've made corrections. I'm using TW to write bash scripts and so forth.

@msample

Found your problem.

Text Wrangler -> Preferences -> Editor Defaults : Uncheck "Use typographer's quotes"

Done. Great catch, I didn't know that feature was checked by default. I usually just jump right into TW. I've gotta go back a check an additional script that might have been stymied. Thanks, Zan.