Solaris Apache2.0.59 Configuration

I wanted to get an OS-level FTP service. After the result was evaluated, the local user could use one CIDR block, but the other CIDR blocks would be slow. So I still want to change the HTTP directory service.
On the other hand, we have installed apache2.0.59 on solaris, which is easier to use. Who knows what is troublesome.

1. Various folders are classified incorrectly.
This is an old problem with the pre-installed software. apache2 is installed in/usr/apache2, And the configuration file http-conf is in/etc/apache2. The application module and
Logs files are stored in/var/apache2.

2. Port permission issues.
For the security management control of Solaris, when using a port less than 1024, it must be completed by users with system permissions such as sys, admin, and so on.
When you start apache2, if you want to use a http://xxx.xxx.xxx.xxx/MODULE, that is, do not want to add a port number, you must use the system permission user to start. Otherwise, you can only use a port number greater than 1024.
The configuration file of the port number is in/etc/apache2/httdp. conf-example. You should change this file to "httdp. conf", and then go to the "Listen" project to find it.

3. Running process file startup Problems
Because it is pre-installed, many files are not created, including folders. Apache2.0.59 is created with A/var/run/folder.
Therefore, an error occurs during running. We recommend that you read error_log to inform you that the/var/run/apache2/httpd. pid file cannot be opened.
In fact, you only need to create the/var/run/apache2 folder.

By now, you can run the testdemo of apache2.

Usage:
#/Usr/apache2/bin/apachectl start
To start

Usage:
#/Usr/apache2/bin/apachectl-k stop
To finally provide services.

Write it here, hey.