Screen saver

[nobrainer]

Through help of this site, I was able to get our new image ready for my September 30th deadline… sort of.

I was doing final testing… and ran into a small problem. I forgot to enable the screen saver password. Apparently on my test box, I had an MCX set to enable it, so whenever I checked to make sure it’s enabled, I found it was. I never noticed that I didn’t have any scripts in my image to manually trigger it.

So, I’ve been googleing trying to figure out how to set the screensaver password via bash script / terminal commands, but apparently my google-fu is failing today. I also don’t trust stuff like that to MCX, from what I’ve noticed MCX settings being applied is flaky at best.

[dead2sin]

Honestly, if you have OD set up and you are binding them to OD, I would only set that type of thing via MCX. I could see wanting to make sure it is set on the image, but one of the main reasons to use OD is for the MCX functionality. If it was always set on your test box via MCX, it should be fair to say that it would be set when you deploy as well.

Nate

[Rusty Myers]

Have you seen this page:

MCX vs the screensaver (and Leopard!)

The content is for MCX, but some of the terminal commands are there and it will tell you what other plists need to be there for it to work.

And this page, #15:
http://www.macosxtips.co.uk/index_files/terminal-commands-for-hidden-settings-in-snow-leopard.html

I’ve been doing this through MCX.

Good luck!

[Author]

Posts