I had the same problem on a Sierra system. I run:
which -a apachectl
to stop the apache by apple version: sudo /usr/sbin/apachectl stop
To see the running processes: ps aux | grep httpd Outputted:
ibook 1359 0,0 0,0 2432804 768 s000 S+ 4:13pm 0:00.00 grep httpd
macOS includes a graphical Activity Monitor application. This application provides an overview of the running processes, memory use, disk and network transfer.
macOS is a FreeBSD based operating system. So if your needs extend beyond Activity Monitor, you can use almost any popular monitoring tool you like, i.e. https://collectd.org
Most probably you're running into one of the following problems:
Wrong handler name: In your question, you wrote that you had the following line:
AddHandler cgi_script .cgi
The underscore is supposed to be a hyphen here, so change that to:
AddHandler cgi-script .cgi
Wrong file extension: Your have specified in your configuration that your Perl scripts ...
By following the tutorial, you have created the file /etc/apache2/users/username.conf which contains the following:
Options Indexes MultiViews FollowSymLinks
Require host localhost
(note that you've replaced "username" with your actual username)
If you want to allow the public ...
TL;DR I turned the offending line into a comment by adding a ˋ#ˋ in the first column and restarted Apache.
To fix this, I followed the Youtube tutorial and opened up the file "httpd-autoindex.conf" using Finder and navigated down to line 21 which has the error. It reads Alias /icons/ "/usr/share/httpd/icons/".
Then I found this tutorial by just searching ...
Launch System Preferences
Select Internet Accounts
Select Add Other Account…
Select CalDAV account
You can then configure the calendar to synchronise with. The calendar must support CalDAV to work with macOS.
It sounds like you do actually not have any configuration files in the /private/etc/apache2/users/ directory, and thus you cannot include them - therefore the configuration check fails.
If you have users on your system with shared a shared Sites folder, you would usually have configuration files in this directory named username.conf with the following ...
I believe nohillside and fsb are indeed correct.
Monitoring the status of a website is something that iOS was never intended to do, except manually. By actually visiting the website and seeing if it is up or not. Using a phone to do such tasks (assuming it is even possible) will likely eat up battery power and might even fail depending on how strong your ...