- Run OS X apps as root
- How to Run GUI Apps as root in Mac OS X
- Launching OS X GUI Apps as root user
- How to Launch GUI Applications from the Terminal
- Opening Mac OS X Applications from the Command Line
- Launching GUI Apps as root from the Command Line
- Creating Shell Aliases for Frequently Launched GUI Apps
- Related
- Enjoy this tip? Subscribe to our newsletter!
- Thank you!
- Related articles:
- 30 Comments
Run OS X apps as root
Aug 13, 2001 · 2 min read
If you’ve used Mac OS X’s command line at all, you may have already seen the sudo command. It lets you execute commands as root (also known as the super-user), which you may want to do periodically for various UNIX system administration tasks. However, sudo can also be used to run any Mac OS X application as root.
This can be very useful: For example, if you want to edit a system configuration file in TextEdit or BBEdit, you’ll have to do so as root or you won’t be able to save changes.
sudo’s b asic syntax is simple. Typing sudo myProcess at a command prompt runs myProcess as root. (If you haven’t used sudo in a while you’ll be prompted for your password first.)
You can run any app the same way, using sudo and the open command. Suppose you want to run the Chess application as root. Open Terminal (in Applications > Utilities) and at the command prompt, type:
sudo open «/Applications/Chess.app»
That’s it! You’re running Chess as root. A few things to note:
- Some applications use the “ .app” extension shown above, while others do not. You can figure out whether an app uses this extension in Terminal. Use the cd command to change to the appropriate folder ( cd /Applications ). Then type ls to see the folder’s contents.
- The quotation marks aren’t actually necessary in the example above. However, they are necessary if any part of the filename or path contains spaces. For example, without quotation marks “ /Applications/My Folder/My App ” will be interpreted by the command line as three items rather than one.
The root user has unlimited power over the operating system. It’s relatively easy, with a few keystrokes, to erase massive amounts of data or render the system unusable. Letting root access fall into the wrong hands is, of course, also very dangerous. Every UNIX system administrator needs to become root from time to time, but you should always use extra caution, and only execute commands as root when absolutely necessary.
Источник
How to Run GUI Apps as root in Mac OS X
Those familiar with the command line know that running things with super user privileges is typically just a matter of using the sudo command. That still holds true with launching GUI apps into the OS X with root privileges, but it’s not just a matter of prepending sudo to the otherwise useful open command, because ‘open’ launches apps as the original user, with or without sudo. The solution instead is to use sudo pointing directly at the executable contained within a given applications package file.
Launching OS X GUI Apps as root user
The command syntax is as follows:
In most cases, that will be applications stored in the /Applications/ directory, and the executable is almost always stored in Package/Contents/MacOS/ as whatever the applications name is:
For example, this command runs the familiar TextEdit app as root:
To launch TextEdit as a background app, meaning it wont close if you close the terminal window, apply the -b flag to sudo:
sudo -b /Applications/TextEdit.app/Contents/MacOS/TextEdit
You can confirm the the application is running as root by using the ps command with grep, again using TextEdit as an example:
ps au|grep TextEdit
Alternatively, you can look at the OS X process management app Activity Monitor and find the application running there as ‘root’ user, as demonstrated in the screenshot up top and the short video below:
If you intend on running a particular app frequently as root, you might consider placing an alias in .bash_profile to shorten the command string.
Despite running as root, not all system files may be modifiable and some may be marked as “Locked” when opened in some apps like TextEdit. That issue can often be resolved by enabling the root user if you have’t done so yet, but not all apps will have that limitation. Nonetheless, for certain tasks like editing the hosts file you’re still better off sticking to the command line and a text based editor, or using an app like BBEdit or TextWrangler.
Источник
How to Launch GUI Applications from the Terminal
We all know how to launch applications from the GUI with a double-click on the icon or clicking on the app in the Dock, and there are numerous ways to do so, and they’re all relatively speedy. If you spend a decent amount of time with the command line though, it’s nice to be able to launch Mac apps directly from there as well. Also, the Terminal has a fair share of applications that run in text based mode, but maybe you wanted to edit a text file in the OS X GUI app TextWrangler rather than the text based nano or vim.
We’re going to demonstrate how to launch any graphical Mac app from the command line of OS X, including how to open specific files from the command line with a GUI app, and how to edit and open those files with root access if it’s necessary.
Opening Mac OS X Applications from the Command Line
The Terminal command to launch OS X gui apps is appropriately called ‘open’ and here is how it works at it’s most simple:
open -a ApplicationName
That will open the defined app named “ApplicationName”.
But open is much more powerful than that. If you just type ‘open’ at the command prompt, you’ll return the basic help file with details on how to properly use the command with a variety of flags and syntax. While the open command exists in all versions of Mac OS X, the abilities vary somewhat depending on what version of OS X the Mac is running. Nonetheless, in modern releases this is what you’ll see:
In other words, example simple command syntax could look like the following, opening “ApplicationName” with the file located at the path ‘/file/to/open’:
open -a ApplicationName /file/to/open
You’ll note you don’t need the full path to the application name, but you would need the full path to a file name.
The usage is likely self explanatory to those who have experience in the command line environment, but for those who are new to the Terminal, don’t be too confused, it is easy to use and we’ll explain. For example, if you want to edit /etc/motd with TextWrangler to change your Message of the Day, but you hate the command line editors nano and vi, here is what you’d type:
$ open -a TextWrangler /etc/motd
Now you can edit these files in the familiar GUI. open is smart enough to know that when you apply the -a flag, you are launching an application so you don’t need to type in its full path. Obviously, it’ll still need the full path to the file you’re editing though.
There are many other usages for the open command rather than just editing text files, so use your imagination and get creative. open could be particularly useful to system administrators who utilize it in a shell script, perhaps to launch a specific GUI application at a scheduled time.
Also worth noting is that if you are launching an application with spaces in its name, you’ll want to add a backslash after each word, opening Adobe Photoshop CS would look like this:
$ open -a Adobe\ Photoshop\ CS
Launching GUI Apps as root from the Command Line
You can even open files with sudo by using the open command if you need to edit a file as root, for example:
sudo open -a TextEdit /tmp/magicfile
This will launch the target file into the desired application as root user, giving full root privileges to edit and modify the file, which is quite helpful for editing many system files. Of course, don’t modify any system file if you don’t know what you’re doing.
Creating Shell Aliases for Frequently Launched GUI Apps
So it’s kind of a pain in the butt to type a full command repeatedly, or to type out all that out over and over again, right? Well let’s make it easier by assigning an alias to an application that gets frequently launched. We’ll take the aforementioned Adobe Photoshop app as an example since the file name is lengthy, so here’s how we’ll do this with the Mac OS X default Bash shell:
First launch the profile or .bash_profile into a text editor:
Ignoring whatever else may be in this file (it could be empty also), add the following to a new line:
alias photoshop=»open -a Adobe\ Photoshop\ CS»
This creates an alias, so that the “open -a Adobe\ Photoshop CS” command is now shortened to simply ‘photoshop’. Save .profile, and you’re on your way! You can use the alias command in conjunction with open for virtually anything, just be sure to pick an alias to a command that doesn’t already exist.
The open command is really handy as you can see, if you have any other great uses for it in OS X, be sure to let us know in the comments.
Related
Enjoy this tip? Subscribe to our newsletter!
Get more of our great Apple tips, tricks, and important news delivered to your inbox with the OSXDaily newsletter.
Thank you!
You have successfully joined our subscriber list.
Related articles:
30 Comments
Thanks for this article – as a Late 2012 Mac Mini user, I have struggled to figure out how to configure X-Plane11 to run real time. I ran the benchmark:
open -a X-Plane.app –args –fps_test=1 –load_smo=Output/replays/test_flight_c4.fdr –pref:_is_ful_ALL=1 –pref:_x_res_full_ALL=1280 –pref:_y_res_full_ALL=720 –pref:_bpp_full_ALL=32
and got:
FRAMERATE TEST: time=93.5, frames=2162, fps=23.12
GPU LOAD: time=93.5, wait=5.7, load=6.1%
so I knew if I made my X-Plane settings 1280×720 windowed, I could get real-time performance, and it works!
How do I write it so that it opens a file, but not a specific file, one that a program could choose?
There is another way of dealing with spaces in this case.
Instead of:
open -a Adobe\ Photoshop\ CS
You could use:
open -a ‘Adobe Photoshop CS’
So, the alias for this would be:
alias photoshop=”open -a ‘Adobe Photoshop CS’ ”
Also, notice the space in the end of the alias (after the CS’ part). It allows you to do more with the command. Example:
Let’s say we got an alias for Chrome. It looks like this:
alias chrome=”open -a ‘Google Chrome’”
In the terminal you want to open a text file with Chrome. Let’s say it’s called ”mydocument.txt”. You will try this in the Terminal:
Which will return an error like this:
Unable to find application named ‘Google Chromemydocument.txt”
Using the alias here is the same as:
open -a ‘Google Chrome’mydocument.txt
So, instead of this we put a space in the alias:
Alias before: alias chrome=”open -a ‘Google Chrome’”
Alias after: alias chrome=”open -a ‘Google Chrome’ ”
Now, when using this space and open a file with the application Alias is equal to:
open -a ‘Google Chrome’ mydocument.txt
The result is that Chrome will open the file mydocument.txt in the browser. Of course, the application itself should be able to display the file.
The same can be used for commands like:
sudo
Allowing you to enable sudo on aliases.
So, the alias for sudo would be like this:
alias sudo=”sudo ”
In that way, you can use (just a example, there is almost no reason at all for this in real world use for Google Chrome):
sudo chrome
To break it down:
-> open -a
As described in the article, the command that will ”Open with the specified application”.
-> ‘Google Chrome’
The exact name of the application as displayed in the Finder without the .app extension.
-> mydocument.txt
The path to the file that will open. In this example, the file is located in the same working directory. But if i was to open a file located in the folder ”Text files from Chanderton” at the Desktop. it would look like this if i was to drag and drop the file in the Terminal after the alias name:
chrome /Users/YourUserName/Desktop/Text\ Files\ from\ Chanderton/mydocument.txt
or not using the application Alias:
open -a ‘Google Chrome’ /Users/YourUserName/Desktop/Text\ Files\ from\ Chanderton/mydocument.txt
—
For the ones that like things to be over the top. You can create the alias like this:
alias chrome=”say ‘Starting Chrome’ | open -a ‘Google Chrome’ ”
or:
alias chrome=”echo ‘🗣 Starting Chrome 👀 ‘; wait | say ‘Starting Chrome’; wait | echo ‘👍 Yeah!’; open -a ‘Google Chrome’ “
[…] X with root privileges, but it’s not just a matter of prepending sudo to the otherwise useful open command, because ‘open’ launches apps as the original user, with or without sudo. The solution […]
How do I also pass command line switches to the app? I’m trying to open VLC with the -v –color switches. (I saw them on the VLC wiki, maybe these are windows only options but the wiki doesn’t specify that.)
Hi
Thanks to you, I can now open my files in Preview using the command line. Now I need to “Save as” in Preview using the command line. Does anyone know how to do it?
Thanks!
Sofia
Try this for a “Save As” replacement in OS X Lion
Hi Matt
Thanks for your reply. but I need to “save as” or “export” from the command line.
I need to convert more than hundred images from .pdf to bmp and to eps and I want to do it in a script. For that, I would like to open these files in Preview and save them in the new format, everything from the command line. Is it possible to “save as” in Preview from the command line?
Thanks
Sofia
[…] command line users, use the “open” command to pass wildcards to ImageOptim for easy scripting and bulk image compression like […]
[…] your hard disk name for this walkthrough. Now here’s the interesting part, typically you can launch applications from the Terminal with the ‘open’ command, but the Lion Recovery drives have a stripped down set of […]
[…] Line, Mac OS X, Tips & Tricks – July 18th, 2011 – Leave a Comment Using the command line open tool, you can immediately launch any URL from the Terminal into the default web browser. The syntax […]
[…] tells the command to only open the file if the header was successfully downloaded. Using ‘open‘ will open httpheader.txt in the default GUI text editor, which is generally Text Edit, but […]
[…] application in Mac OS X with a little command line magic. Using the ‘open’ command to launch GUI apps from the Terminal, we can run a new instance of any app, even if it is already […]
so how do i open a folder in the terminal to have it open as a gui folder? (not cd command – that just opens it in the terminal itself)
for instance can i say
open /etc? and have the gui window pop up?
so open /etc would open /etc in the Finder
[…] osxdaily David Miller O’reilly wiki bash ss64 This entry was posted in bash, osx, terminal. Bookmark […]
[…] How to Launch GUI Applications from the Terminal – OS X Daily (tags: alias command bsd howto macosx terminal tip open apple launch opensource unix tips osx shell macos applications application commandline macintosh mac from gui article os guide) […]
[…] Come lanciare le applicazioni di Mac OS X dalla linea di comando (Terminale) How to Launch GUI Applications from the Terminal – OS X Daily. […]
anyone know how I can do adobe updates through the command line.? I want to send unix commands with ARD to adobe updater to install the updates.
a search by Pacifist (of the base.pkg and the bsd.pkg) on the osx leopard retail installer dvd turns up NO RESULT for a command named “open”!
are you sure that this command was available even in tiger?!
you really need to be more precise about the context of the ‘open’ command vis a vis the (bash) shell …
what are the prerequisites & dependencies that must already be setup in order – for instance – to run the ‘open’ command from the osx installer dvd?!
i have created a custom boot disk that adds an extra folder of diagnostic utilities to help troubleshooting … but none of those apps will run even when my local path already is located at the (new) special utility folder (ls sees the contents of the directory just fine).
i suspect that apple’s path info (on the bootable dvd) is locked down, so osx can not even see the ‘open’ command (because it is not part of the bsd userland that is loaded from the boot dvd) — if this is true, then i suppose it is just a matter of editing some config files (on the disk image) before burning another custom installer, correct?
If so, then it would be useful for you to articulate a flight-check/checklist of which files must be setup in what way in order to allow a given functionality under what circumstances!
obviously, my specific example is the one i am most interested in 🙂
ps: it should be noted that the reason i am want to launch specific apps /from the installer disc/ is precisely because i do not wish to complete the only type of installation that is available to me (in this case, unfortunately, a fresh install, which will wipe my current partition) … i have not backed it up yet (long story) but i want the chance now to dump everything on the NAS – alas, firewire target mode is not available because that port seems dead on my Mini 🙁 …
i dont know exactly what app will allow me to backup to the NAS (carbon copy cloner, disk utility, etc), but no matter which one i will need to use, i know i will need to use the ‘open’ command from a bash shell that has a default restriction on how much of the global path is visible to the bootable installer dvd!
i am sure i am not the only person who will be ever caught with a blown-up partition on a machine that cant use firewire target mode – so some clarification about the prereqs in the path environment variables would be super appreciated!
Источник