Timeline for OSX, Failed to listen on 0.0.0.0:80 (reason: Permission denied)
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 20, 2018 at 16:56 | history | edited | Giacomo1968 | CC BY-SA 4.0 |
added 4 characters in body
|
| Mar 20, 2017 at 10:17 | history | edited | CommunityBot |
replaced http://superuser.com/ with https://superuser.com/
|
|
| Jan 30, 2014 at 18:32 | vote | accept | Justin | ||
| Jan 29, 2014 at 21:07 | comment | added | Yarek T | And IIRC OSX has launchd, its a bit like inetd, the internet super server. Its a binary that listens on all ports and spawns a corresponding process whenever a specific port is hit by a request | |
| Jan 29, 2014 at 21:04 | comment | added | Yarek T | Oh yea totally forgot, you could setuid on the php binary (or wrap it in a shell script). Its insecure, but as a dev environment it might just do | |
| Jan 29, 2014 at 20:46 | comment | added | Ben Voigt |
you didn't turn off port number->name lookup, so it might be outputting TCP:http (I don't know about Mac lsof, but netstat on other OSes would). Check the output of just sudo lsof -i TCP to see what format it is in.
|
|
| Jan 29, 2014 at 20:38 | comment | added | Justin |
When I do sudo lsof -i TCP:80 | grep LISTEN I get no results.
|
|
| Jan 29, 2014 at 20:27 | comment | added | Ben Voigt | For that, see Who is listening on a given TCP port on Mac OS X? | |
| Jan 29, 2014 at 20:15 | comment | added | Justin | How can I see what is currently using it? I'm guessing it's something that happens at start-up. | |
| Jan 29, 2014 at 20:13 | comment | added | Ben Voigt | Since you get a page from localhost, then means some software on your computer is already using port 80. Two programs can't use the same port at the same time. | |
| Jan 29, 2014 at 20:09 | answer | added | Yarek T | timeline score: 16 | |
| Jan 29, 2014 at 20:04 | history | asked | Justin | CC BY-SA 3.0 |