In Mac, the root directory can also be referred as Macintosh HD as this will show you the root directory files and folders. By default you won’t find it in Finder and desktop as most of the users do not need to access the system files and folders. How to run a script as root on Mac OS X? closed Ask Question Asked 12 years, 7 months ago. Active 10 years ago. Viewed 211k times 36. Mac OS X Snow Leopard (version 10.6) is the seventh major release of macOS, Apple's desktop and server operating system for Macintosh computers. Snow Leopard was publicly unveiled on June 8, 2009 at Apple’s Worldwide Developers Conference.On August 28, 2009, it was released worldwide, and was made available for purchase from Apple's website and retail stores at the price of US$29 for a. Mac OS and iOS trust 165 root certificates in total. This is 23 fewer total certificates than the previous version (in El Capitan). Only two new roots have been added. (Update: The ISRG Root, used by Let’s Encrypt, was added in a later update). Of the 165 root certificates, 152.
May 4, 2013 11:51 PM
Great guide, thanks John.
Just a note, in case anyone has the same issue. At first I couldn't get this to work. I tried logging out and back in (still no joy), then restarting the mac (still no joy).
Try doing both of those first. However, if, like me, you still can't get the local host site to load, try the following: You should find a file at /Library/WebServer/Documents/index.html.en . This contains the text 'It works!' referred to in the post. What I did was duplicate that file in the same folder and changed the duplicate's name to 'index.html', leaving the original in situ.
Both local and user sites then loaded. After which, I was able to delete the duplicated file and everything now works without issue. Just to be clear, leave the original file index.html.en where it is, untouched and unharmed throughout this step.
Not sure why I had to take this mysterious detour - probably something local to my machine, but if you're having trouble after following the guide above, see if it helps.
May 4, 2013 11:51 PM Caught in my soch mac os.
Killing a root process | 13 comments | Create New Account
Click here to return to the 'Killing a root process' hint |
The following comments are owned by whoever posted them. This site is not responsible for what they say.
after you su to root in the terminal, type 'ps -ax' and you should see all processes, find the one you want to kill, and 'kill -9 #INSERT PROCESS ID HERE#' i forget what the -9 is for, but it's good in case something doesn't want to be killed, so -9 is kind of like a kill with extreme prejudice. You can always read the man pages.. Science out of control mac os.
The -9 flag will terminate the process immediately without giving the process a chance to exit cleanly. Using -HUP (hangup) is 'nicer' in that the program may be able to shut itself down, but OTOH -HUP doesn't always work and you have to resort to -9 anyway.
For more information open your terminal and type 'man kill'.
For more information open your terminal and type 'man kill'.
The usual way to restart a daemon to reconfigure it is to use kill -HUP. Dunno if it works for mysql but I've done this many times for inetd on solaris 2.6.
Your description of -HUP sounds more like the definition of -TERM (-15).
Kill -HUP is sometimes used to tell a process to restart/refresh. Often it does absolutelty nothing. The author of the program decides what to do in response to a -HUP.
Kill -TERM tells a process to shutdown (TERMinate) and gives the process the opportunity to do so cleanly.
kill -KILL (aka kill -9) is a shutdown that doesn't allow the process to shutdown cleanly.
If you type 'kill -l' (that's an 'L' not the number one) you'll get a list of signals. Count them off to find the numeric equivalent.
kill -l
HUP INT QUIT ILL TRAP ABRT EMT FPE KILL BUS SEGV SYS PIPE ALRM TERM URG STOP TSTP CONT CHLD TTIN TTOU IO XCPU XFSZ VTALRM PROF WINCH INFO USR1 USR2
Having access to the root account is a sharp & powerful double-edged sword. Kill -HUP is sometimes used to tell a process to restart/refresh. Often it does absolutelty nothing. The author of the program decides what to do in response to a -HUP.
Kill -TERM tells a process to shutdown (TERMinate) and gives the process the opportunity to do so cleanly.
kill -KILL (aka kill -9) is a shutdown that doesn't allow the process to shutdown cleanly.
If you type 'kill -l' (that's an 'L' not the number one) you'll get a list of signals. Count them off to find the numeric equivalent.
kill -l
HUP INT QUIT ILL TRAP ABRT EMT FPE KILL BUS SEGV SYS PIPE ALRM TERM URG STOP TSTP CONT CHLD TTIN TTOU IO XCPU XFSZ VTALRM PROF WINCH INFO USR1 USR2
It's not by accident that Apple locked it out by default, and that decision
shouldn't be crossed lightly.
In most cases, `sudo` is a far safer tactic. It allows you to run a command
as another user (such as of course the root account), and you're not left in
that other users account where it is all too easy to make a mess of things.
Better by far here would be to find & kill the process in question this way:
That last line is a test to make sure it worked. If it didn't, try
`kill`ing again with numbers increasing from 5 to 9 (shifting from safer
'let it die gracefully' commands to riskier 'alright just shut down NOW'
commands):
`kill`ing again with numbers increasing from 5 to 9 (shifting from safer
'let it die gracefully' commands to riskier 'alright just shut down NOW'
commands):
It should work by the time you get to -9, but hopefully sooner.
Of course, as another poster noted, this isn't the right way to do it
anyhow. The mysql distribution should have included a shutdown script. If
I knew mysql better I'd quote the command & syntax myself, but the other
poster already said it and, moreover, your mysql documentation should
surely have mentioned how to start & stop the server properly.
anyhow. The mysql distribution should have included a shutdown script. If
I knew mysql better I'd quote the command & syntax myself, but the other
poster already said it and, moreover, your mysql documentation should
surely have mentioned how to start & stop the server properly.
Read The Funny Manual!
Part of the previous post is BAD advice. Doing a kill -5, -6, -7, -8, before resorting to -9 is nonsense. To kill off a process, try -15 then -9. Each numeric argument corresponds to a different signal. The 'kill' command is a misnomer since it's a tool to send signals to processes, and only one of the signals happens to be '-9', the kill signal. For example, kill -8 is equivalent of telling the process it has experienced a floating-point exception and you want a core dump created (a huge debugging file, useless in this context). Here's a list of signals, their numbers, names and descriptions. The info came from 'man sigaction', I added the numbers for clarity.
:)I stand corrected. Very interesting.
Phillip,
To see all the processes type 'ps aux'. Personally I created/edited the .cshrc file in my home directory to include a line with the following
alias ps 'ps aux'
and once you launch a new terminal window ps will now give you all the details to identify pid's on running processes.
yuri
To see all the processes type 'ps aux'. Personally I created/edited the .cshrc file in my home directory to include a line with the following
alias ps 'ps aux'
and once you launch a new terminal window ps will now give you all the details to identify pid's on running processes.
yuri
Surely it's a bad idea to shutdown any kind of database server this way (anybody who's had to force-quit FileMaker will know what i mean..),
Has anybody tried:
cd /usr/local/mysql/bin
./mysqladmin shutdown
Has anybody tried:
cd /usr/local/mysql/bin
./mysqladmin shutdown
As many users have discovered you can't get the mysql daemon to quit using mysqladmin shutdown. This is a bug that exists for all BSD Unices, and not just MacOS X. Some have suggested it is because the signals that are generated by mysqladmin shutdown are blocked in some way. There are a whole bunch of threads about it all over the net, as a search on Google for terms like 'mysql admin shutdown kill can't' will attest.
If anyone finds some solution I'd love to hear about it. For now it looks as if the only SAFE way to shut it down is to turn off the automatic startup of mysql and restart the computer.
If anyone finds some solution I'd love to hear about it. For now it looks as if the only SAFE way to shut it down is to turn off the automatic startup of mysql and restart the computer.
You can sudo kill it if you don't have your root account enabled.
sudo kill process id
sudo kill process id
Mysql on OS X is ugly. Theoretically you should be able to shut it down cleanly with the
shutdown command from within mysqladmin, but that doesn't sem to work.
I have seen it written that the only clean way to deal with the problem is to
keep the shell which launched the safe daemon, interrupt it with CTL-Z, do
a ps and kill the spawned daemon brood, then kill the broodmaster.
Please correct me if i am wrong. I am waiting for a package which one can have
real confidence in. I have installed mysql on linux, linux ppc and OS X from original
sources. It integrates nicely into the redhat linux daemon start/stop runlevel scheme,
but i don't know how this issue is handled by Mac OS X.
shutdown command from within mysqladmin, but that doesn't sem to work.
I have seen it written that the only clean way to deal with the problem is to
keep the shell which launched the safe daemon, interrupt it with CTL-Z, do
a ps and kill the spawned daemon brood, then kill the broodmaster.
Please correct me if i am wrong. I am waiting for a package which one can have
real confidence in. I have installed mysql on linux, linux ppc and OS X from original
sources. It integrates nicely into the redhat linux daemon start/stop runlevel scheme,
but i don't know how this issue is handled by Mac OS X.
Tennis4two - The Roots Mac Os 11
Sending a server process a normal kill signal first is a good idea, lets it know that
it should exit gracefully and gives it a chance to behave like a gentleman :)
By the way, mysql is a very bad citizen, see my post below.
Edmund
it should exit gracefully and gives it a chance to behave like a gentleman :)
By the way, mysql is a very bad citizen, see my post below.
Edmund