Can I end all httpd processes? (OSX, 10.7.4, Lion)

38,665

Solution 1

Mountain Lion removed the Web Sharing option, maybe you upgraded and had it running some time in the past? Anyway, you'll need to open Terminal for this:

sudo killall httpd
sudo launchctl unload /System/Library/LaunchDaemons/org.apache.httpd.plist

The first will fail if you've already killed all the processes, the second disables startup.

Solution 2

Open the Sharing preference pane in System Preferences and uncheck Web Sharing.

Share:
38,665

Related videos on Youtube

dmanexe
Author by

dmanexe

Web developer, bicycle fanatic, reddit lurker, news reader and fist pumper.

Updated on September 18, 2022

Comments

  • dmanexe
    dmanexe almost 2 years

    I have several instances of httpd running on my Mac. Don't need to run a web server, would like to end them all, as they add up to about 100mb of unnessecary RAM. What is the configuration that sets them to run? How can I disable it?

  • HikeMike
    HikeMike over 11 years
    FWIW, this option has been removed from Mountain Lion.
  • Gutsygibbon
    Gutsygibbon over 11 years
    So why the downvote? This method works... not something hard.You can just google this
  • HikeMike
    HikeMike over 11 years
    He's on 10.7.4 according to the Q.
  • Gordon Davisson
    Gordon Davisson over 11 years
    httpd is normally started by /System/Library/LaunchDaemons/org.apache.httpd.plist, and changing the contents of /System is not recommended. Using launchctl to manage it (as @Jeff recommended) is a much better way to do it.
  • rymo
    rymo about 11 years
    This solved it for me on 10.7.5; even though Web Sharing exists and is unchecked in System Preferences, httpd was surviving/respawning through killall until using this launchctl command (but this particular system might have other issues)
  • Nicolas Manzini
    Nicolas Manzini over 10 years
    nope still running httpd on my lion
  • Martyn Chamberlin
    Martyn Chamberlin over 7 years
    Wow! I was getting this error with MAMP Pro, and running the above fixed it. cl.ly/010Y2g2V3v3M/Image%202017-01-23%20at%201.35.59%20PM.pn‌​g