Odd question relating to preinstall scripts and administrator access
Odd question relating to preinstall scripts and administrator access
- Subject: Odd question relating to preinstall scripts and administrator access
- From: Cameron Pulsford <email@hidden>
- Date: Thu, 31 Jul 2008 13:54:10 -0400
So I seem to have the opposite problem most people have... I am
installing something that needs administrator access but I need to run
a preinstall script that not only doesn't need these rights, it can't
have these rights. I need to run a script that does stuff with
"launchctl unload" and when that is given root access it defaults to
root, even if the explicit path you give it to unload is ~/Library/xxx
for example. That's at least what I have gathered after some research.
When I run the script from the terminal it works, but when I run "sudo
thescript" it doesn't work.
I tried modifying my script like this...
realUserName=`echo $USER`
sudo -u $realUserName launchctl unlead $HOME/Library/LaunchAgents/
com.racepoint.*.plist
and in the console I still get the same error message "launchctl:
Dubious ownership on file (skipping) /Users/xxx/Library/LaunchAgents"
and then the installer fails.
Just to test I made a new package that just did some bogus stuff that
didn't need administrator access, and I had it run the same prelaunch
script and it worked great. Sorry if this is confusing but essentially
I need a script to run without super user privileges but the component
thats getting installed after the prelaunch script does. Any ideas?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden