Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Software - Troubleshooting and Discussion > Developer Center > stopping commands

stopping commands
Thread Tools
Fresh-Faced Recruit
Join Date: Feb 2007
Status: Offline
Reply With Quote
Feb 17, 2009, 01:12 PM
 
I'm trying to limit users from copying applications out of the /Applications folder, and my idea was to create a script that would stop whatever command is running under the GUI when a user drags an item out of /Applications (presumably cp). Is this feasible? If so, how would I start writing a script that would stop it?

Thanks!
     
Clinically Insane
Join Date: Oct 2001
Location: San Diego, CA, USA
Status: Offline
Reply With Quote
Feb 17, 2009, 01:24 PM
 
This is not feasible, at least not that simply. The Finder does not use cp for its copying — it uses the same underlying system calls that cp uses. You could probably patch the file copying routines, but that isn't nearly as easy.
Chuck
___
"Instead of either 'multi-talented' or 'multitalented' use 'bisexual'."
     
Posting Junkie
Join Date: Oct 2005
Location: Houston, TX
Status: Offline
Reply With Quote
Feb 17, 2009, 08:11 PM
 
Set the permissions to execute only?
It's an amusing idea, but I don't even know if that would work.
     
Clinically Insane
Join Date: Oct 2001
Location: San Diego, CA, USA
Status: Offline
Reply With Quote
Feb 17, 2009, 08:21 PM
 
That doesn't work. If the executable isn't readable, Finder won't even try to open it.
Chuck
___
"Instead of either 'multi-talented' or 'multitalented' use 'bisexual'."
     
Mac Elite
Join Date: Oct 1999
Location: San Jose, Ca
Status: Offline
Reply With Quote
Feb 17, 2009, 09:12 PM
 
The solution is to put a folder into the .app bundle that the users in question can't read. The finder will get to that folder and stop. They might get something, but if you name the folder with an 'A' then they won't get anything meaningful.
     
Clinically Insane
Join Date: Oct 2001
Location: San Diego, CA, USA
Status: Offline
Reply With Quote
Feb 18, 2009, 01:45 AM
 
Originally Posted by larkost View Post
The solution is to put a folder into the .app bundle that the users in question can't read. The finder will get to that folder and stop. They might get something, but if you name the folder with an 'A' then they won't get anything meaningful.
Oh, very clever. That would work.
Chuck
___
"Instead of either 'multi-talented' or 'multitalented' use 'bisexual'."
     
   
Thread Tools
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Top
Privacy Policy
All times are GMT -5. The time now is 07:53 PM.
All contents of these forums © 1995-2011 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.7 © 2000-2011, Jelsoft Enterprises Ltd., Content Relevant URLs by vBSEO 3.3.2