Forum Replies Created
-
AuthorPosts
-
[email protected]
Participantwhoops, made a mistake…
how to tell dsconfigldap to use rfc2307 and not [b]Open Directory[/b]
June 18, 2009 at 9:31 am in reply to: Need a _very_ robust backup mechanism for large Mac OS X 10.5 client footprint #376458[email protected]
Participanttake a look at archiware’s [url=http://www.archiware.com/index.php?hp=472]backup2go[/url]
[email protected]
Participanthi all,
tnx for the input.
to wrap up:to disable sleep when a user is logged in, run following script as a loginhook
[code]
/usr/bin/pmset -c sleep 0
/usr/bin/pmset -c displaysleep 5
/usr/bin/pmset -c disksleep 0
/usr/bin/pmset -c lessbright 0
/usr/bin/pmset -c halfdim 0/usr/bin/pmset -b sleep 0
/usr/bin/pmset -b displaysleep 5
/usr/bin/pmset -b disksleep 5
/usr/bin/pmset -b lessbright 1
/usr/bin/pmset -b halfdim 1
[/code]to enable sleep when no user is logged in, run following script as a logouthook
[code]
/usr/bin/pmset -c sleep 30
/usr/bin/pmset -c displaysleep 60
/usr/bin/pmset -c disksleep 0
/usr/bin/pmset -c lessbright 0
/usr/bin/pmset -c halfdim 0/usr/bin/pmset -b sleep 5
/usr/bin/pmset -b displaysleep 5
/usr/bin/pmset -b disksleep 5
/usr/bin/pmset -b lessbright 1
/usr/bin/pmset -b halfdim 1
[/code]these values may not make sense for your environment, adjust where you think you should 🙂
for the “at random” autowake, go to system preferences > energy saver > schedule and enable “sart up or wake” and set a time. than copy /Library/Preferences/SystemConfiguration/com.apple.AutoWake.plist to somewhere and rename it 0.com.apple.AutoWake.plist
set another wakeup time in system preferences and again copy the com.Apple.AutoWake.plist rename this file to 1.com.Apple.AutoWake.plist and continue these last steps until you’ve collected 10 files (named 0 to 9)
put them in a folder and add following script to that folder[code]
/bin/rm /Library/Preferences/SystemConfiguration/com.apple.AutoWake.plist
/bin/cp /Library/Deployment/AutoWake/`jot -n -r 1 0 9`.com.apple.AutoWake.plist /Library/Preferences/SystemConfiguration/com.apple.AutoWake.plist
[/code]it picks a number from 0 to 9 and takes that file and places it in the right place.
next, make sure this script runs at least once:
– using a suicidal startupitem
– using your favorite software distribution system
– …to keep my login- and logouthooks clean, i often use a login- and logoutwrapper. the loginwrapper is a simple script that runs every script in a given directory, the logoutwrapper is the same but for another directory and at logout 🙂
again, you can than drop login- and or logoutscripts using your favorite softare distribution system[email protected]
ParticipantHi all,
create different groups in directory infrastructure is not the way we want to go… there are enough groups to take care about 🙂i was more thinking about something like:
create a set of 10 autowake.plist files and store them somewhere on the system (i often use a folder /Library/Deployment/blabla)
so let’s create 10 different autowake files with 10 different wake times defined
/Library/Deployment/AutoWake/01.com.apple.autowake.plist
/Library/Deployment/AutoWake/02.com.apple.autowake.plist
…
create a startupitem or something else that does the jobgenerate number between 01 and 10 and name that number VARNR
cp /Library/Deployment/AutoWake/$VARNR.com.apple.autowake.plist /Library/Preferences/SystemConfiguration/com.apple.autowake.plistany thoughts on this?
any ideas how to generate a random number between 01 and 10 or between 0 and 9?September 9, 2008 at 9:42 am in reply to: Why do pkg’s install on / instead of $CURRENT_IMAGE_MOUNT #374029[email protected]
Participantok,sure, makes sense…
the reason i wanted to set things this way, is because it’s easy ‘recyclable’ and easy to change in other deployment scenarios.
to reply on knowmad,
[quote] the upshot of your reply seems to be that if you put the updates where they belong then it works and if you put them where they don’t belong than it does not work…… am I missing something? [/quote]
what i mean, it did work with updates from apple but it didn’t with pkg’s i had created. now i understand it has nothing to do with how i made those pkg’s. (was not sure about that)i’ll try the suggestions and see what works best for me
September 8, 2008 at 6:47 pm in reply to: Why do pkg’s install on / instead of $CURRENT_IMAGE_MOUNT #374025[email protected]
Participanthi all,
i’ve made 2 changes to the instadmg script:
[code]ASR_FILESYSTEM_NAME=”Macintosh HD”[/code] for the name of the resulting dmg when mounted and
[code]if [ “$IMAGE_FILE” == “$INSTALLER_FOLDER/Mac OS X Install Disc 1.dmg” ] || [ “$IMAGE_FILE” == “$INSTALLER_FOLDER/Mac OS X Upgrade DVD.dmg” ][/code]
so that a ‘drop in dvd’ can be used as base os.one of the scripts i run (as postinstall on a empty pkg) is for setting the energy saver
the contents of the script are:
[code]
pmset -c sleep 0
pmset -c displaysleep 60
pmset -c disksleep 0
pmset -c lessbright 0
pmset -c halfdim 0
pmset -b sleep 5
pmset -b displaysleep 3
pmset -b disksleep 5
pmset -b lessbright 1
pmset -b halfdim 1
[/code]
instead of applying these settings to the dmg, they are applied to the system where i run the instadmg.bash script. the packagemaker project and the pkg are on my .mac public folder (my .mac login is tuke)when i place system updates in the correct folder, they are applied as they should to the resulting dmg
i haven’t used installerchoices yet (still on my todo list…)
-
AuthorPosts
Recent Comments